{"version":"2.1.257","anchor":"mcp-tool-results-now-carry-resource-links-separately-from-m","canonical_anchor":"mcp-tool-results-now-carry-resource-links-separately-from-m","heading":"MCP tool results now carry resource_links separately from _meta","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/mcp-tool-results-now-carry-resource-links-separately-from-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### MCP tool results now carry resource_links separately from _meta\n\nMCP tool results now carry resource links as their own field so hosts can render referenced files directly.\n\nTool result messages now include a `resource_links` field that collects the raw `resource_link` content blocks returned by an MCP tool (up to 50 links or 64 KiB), as a sibling to `_meta` on `tool_use_result.mcpMeta`. This lets a host render referenced files directly instead of parsing the `[Resource link: NAME] URI` text line; it is absent for subagent tool results. Both live MCP tool calls and MCP task-based tool calls now capture and pass through `resourceLinks`\/`resource_links`, including in the background-task terminal summary.\n\n- Area: MCP\n- Names: `resource_links`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}