instead of embedded, let us link

Author: kentcdodds

exercises/03.resources/01.solution.simple/src/resources.ts

@@ -6,9 +6,9 @@ export async function initializeResources(agent: EpicMeMCP) {
 		'epicme://tags',
 		{
 			title: 'Tags',
-			description: 'All tags',
+			description: 'All tags currently in the database',
 		},
-		async (uri: URL) => {
+		async (uri) => {
 			const tags = await agent.db.getTags()
 			return {
 				contents: [

exercises/03.resources/02.solution.template/src/resources.ts

@@ -7,7 +7,7 @@ export async function initializeResources(agent: EpicMeMCP) {
 		'tags',
 		'epicme://tags',
 		{
-			title: 'All tags',
+			title: 'Tags',
 			description: 'All tags currently in the database',
 		},
 		async (uri) => {
@@ -31,7 +31,7 @@ export async function initializeResources(agent: EpicMeMCP) {
 		}),
 		{
 			title: 'Tag',
-			description: 'A tag by ID',
+			description: 'A single tag with the given ID',
 		},
 		async (uri, { id }) => {
 			const tag = await agent.db.getTag(Number(id))
@@ -54,8 +54,8 @@ export async function initializeResources(agent: EpicMeMCP) {
 			list: undefined,
 		}),
 		{
-			title: 'Entry',
-			description: 'A single entry',
+			title: 'Journal Entry',
+			description: 'A single journal entry with the given ID',
 		},
 		async (uri, { id }) => {
 			const entry = await agent.db.getEntry(Number(id))

exercises/03.resources/03.problem.list/src/resources.ts

@@ -7,8 +7,8 @@ export async function initializeResources(agent: EpicMeMCP) {
 		'tags',
 		'epicme://tags',
 		{
-			title: 'All tags',
-			description: 'All tags',
+			title: 'Tags',
+			description: 'All tags currently in the database',
 		},
 		async (uri) => {
 			const tags = await agent.db.getTags()
@@ -32,8 +32,8 @@ export async function initializeResources(agent: EpicMeMCP) {
 			list: undefined,
 		}),
 		{
-			title: 'A single tag',
-			description: 'A single tag',
+			title: 'Tag',
+			description: 'A single tag with the given ID',
 		},
 		async (uri, { id }) => {
 			const tag = await agent.db.getTag(Number(id))
@@ -58,8 +58,8 @@ export async function initializeResources(agent: EpicMeMCP) {
 			list: undefined,
 		}),
 		{
-			title: 'A single entry',
-			description: 'A single entry',
+			title: 'Journal Entry',
+			description: 'A single journal entry with the given ID',
 		},
 		async (uri, { id }) => {
 			const entry = await agent.db.getEntry(Number(id))

exercises/03.resources/03.solution.list/src/resources.ts

@@ -40,7 +40,7 @@ export async function initializeResources(agent: EpicMeMCP) {
 		}),
 		{
 			title: 'Tag',
-			description: 'A tag by ID',
+			description: 'A single tag with the given ID',
 		},
 		async (uri, { id }) => {
 			const tag = await agent.db.getTag(Number(id))
@@ -72,8 +72,8 @@ export async function initializeResources(agent: EpicMeMCP) {
 			},
 		}),
 		{
-			title: 'Entry',
-			description: 'A single entry',
+			title: 'Journal Entry',
+			description: 'A single journal entry with the given ID',
 		},
 		async (uri, { id }) => {
 			const entry = await agent.db.getEntry(Number(id))

exercises/03.resources/04.problem.completion/src/resources.ts

@@ -7,8 +7,8 @@ export async function initializeResources(agent: EpicMeMCP) {
 		'tags',
 		'epicme://tags',
 		{
-			description: 'All tags',
-			title: 'All tags that exist in the database currently',
+			title: 'Tags',
+			description: 'All tags currently in the database',
 		},
 		async (uri) => {
 			const tags = await agent.db.getTags()

exercises/03.resources/05.problem.embedded/README.mdx renamed to exercises/03.resources/05.problem.linked/README.mdx

@@ -1,27 +1,39 @@
-# Embedded Resources
+# Linked Resources
 
 👨‍💼 You've already made your resources discoverable and accessible—now let's make
-them even more useful! In this step, you'll learn how to embed a resource
+them even more useful! In this step, you'll learn how to link a resource
 directly in your tool responses.
 
 Why does this matter? Sometimes, a tool's output isn't just plain text—it might
-be a file, a database record, or some other structured data. By embedding
+be a file, a database record, or some other structured data. By linking to
 resource references, you enable clients (and LLMs) to follow links to additional
 context, download files, subscribe to updates, or fetch related data on demand.
 
 Your goal in this step:
 
 - Update your tools so that, when they create a tag, we tell them it was created
-  and also include a reference to the tag (using the `type: 'resource'` content
-  type in the response).
+  and also include a reference to the tag (using the `type: 'resource_link'`
+  content type in the response).
 - Make sure the resource includes the correct URI and metadata, so clients can
   easily fetch the resource if they want more details.
-- Include the resource itself in the response, so clients can use it directly.
 
 This pattern unlocks powerful workflows—tools and resources working together to
 provide richer, more actionable results.
 
+Here's an example of the content type if we were to link to a taco ingredient
+resource:
+
+```json
+{
+	"type": "resource_link",
+	"uri": "taco://ingredients/1",
+	"name": "Lettuce",
+	"description": "A delicious lettuce ingredient",
+	"mimeType": "application/json"
+}
+```
+
 To test this out, create a new tag and notice the resource is included in the
 response.
 
-- 📜 [MCP Spec: Tools (Embedded Resources)](https://modelcontextprotocol.io/specification/2025-06-18/server/tools#embedded-resources)
+- 📜 [MCP Spec: Tools (Resource Links)](https://modelcontextprotocol.io/specification/2025-06-18/server/tools#resource-links)

exercises/03.resources/05.problem.embedded/package.json renamed to exercises/03.resources/05.problem.linked/package.json

@@ -1,5 +1,5 @@
 {
-  "name": "exercises_03.resources_05.problem.embedded",
+  "name": "exercises_03.resources_05.problem.linked",
   "private": true,
   "type": "module",
   "scripts": {