{"version":"2.1.287","anchor":"mcp-structuredcontent-omitted-when-too-large","canonical_anchor":"mcp-structuredcontent-omitted-when-too-large","heading":"Oversized structured results from MCP tools are now left out","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/mcp-structuredcontent-omitted-when-too-large","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Oversized structured results from MCP tools are now left out\n\nStructured data from an MCP tool is now dropped from the result Claude sees when it is over a size limit, with a marker recording this\n\n**Unclear.** The exact size limit is not known.\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools. Their tools can return structured content, meaning data laid out in fixed fields, alongside the usual text. If that structured content is over a size limit, Claude Code now leaves it off the result message. It sets `structuredContentOmitted` on the tool result so the gap is recorded.\n\nTwo cases are exempt:\n\n- tools that declare a UI panel through `_meta.ui`\n\n- in-process SDK servers, meaning MCP servers running inside the same program as Claude Code\n\n**Why**\n\nVery large tool results no longer fill up the conversation. Claude does not see the structured part of those results, though, so an MCP tool that returns a lot of structured data will reach Claude without it.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}