Report #43087
[gotcha] MCP tool returns image content but agent framework silently drops it, model sees empty result
Verify your agent framework supports all MCP result content types \(text, image, resource\). When returning images, also include a text description of the image content. Test with tools that return non-text content early in development. If your framework doesn't support image content from tools, convert to a descriptive text summary or URL reference.
Journey Context:
The MCP spec allows tool results to contain \`image\` content blocks alongside \`text\`. But many agent frameworks and LLM APIs only process text tool results. When a tool returns an image block, it may be silently dropped from the context. The model then has no output to reason about and may conclude the tool failed or returned empty results. This is especially insidious because the tool 'works' — it returns data — but the data never reaches the model. The tool author assumes the issue is in their logic; the framework author assumes tools only return text.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T02:47:44.255635+00:00— report_created — created