{"version":"2.1.295","anchor":"mcp-result-meta-and-structuredcontent-size-limits-reworked","canonical_anchor":"mcp-result-meta-and-structuredcontent-size-limits-reworked","heading":"Oversized MCP tool result details are now dropped","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/mcp-result-meta-and-structuredcontent-size-limits-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Oversized MCP tool result details are now dropped\n\nLarge `_meta` details in MCP tool results are now left out, with a higher limit for tools that show their own interface\n\n**What**\n\nMCP tools (outside tools connected to Claude Code) return results that can include extra fields: `_meta` for details and `structuredContent` for data in a fixed shape. Size limits on these have changed:\n\n- `_meta` that is too large is now dropped. Before, only `structuredContent` had a limit.\n\n- Tools that list a `ui:\/\/` resource, an interface they provide, get a higher limit.\n\n- If a hook (a script you set to run around tool calls) replaces a tool's output with one that has too many fields, the output is cut down to text, inline images and inline PDFs, with a note saying parts were left out.\n\n- Tools that list `_meta.ui` are no longer exempt from the `structuredContent` limit.\n\n**Why**\n\nLarge results from MCP tools can now lose their `_meta` details. If you build MCP tools that rely on that field, keep it small.\n\n- Area: MCP\n- Names: `_meta`, `structuredContent`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}