Error message
The message lists every problem in the payload, separated by; . Each problem is one of:
{location} names the block: content[1] for a block in a user message, outputs[0].content[2] for the third
block of the first tool output.
For example, a user message whose content[0] is a tool_use block and whose content[1] is a 600,000-byte image
reports three problems. The image is over the per-image limit, and with it the payload is over the total:
When this error occurs
POST /agents/conversations/{id}/runs checks the blocks in its payload before it starts the run, in the user
message and in each tool output’s content:
The platform writes
tool_use, tool_result and reasoning blocks itself, so a payload that includes one gets this
error.
A body that doesn’t decode at all is a different 400, with an {error, error_description} body. This covers an
unknown block type, and an image with any of these:
- a
media_typeother thanimage/jpeg,image/png,image/giforimage/webp; - a
sourcewhosetypeisn’tbase64, such as a URL; datathat isn’t valid base64. Send the raw image bytes base64-encoded with the standard alphabet. Don’t send a data URL (data:image/png;base64,...); send only the part after the comma.
How to fix
The error lists every problem at once, so fix them all before you send the run again.- Empty user message. Send at least one
textorimageblock, or sendtextas a string. - A block other than text or an image. Keep only
textandimageblocks incontent. To return structured data from a client tool, serialize it to a string and send it as text. - An image over 512 KB. Downscale or recompress the image before you send it. A JPEG or WebP is usually much smaller than a PNG of the same picture.
- Over the total, or more than 20 images. Send fewer images per run, and the rest with the next run. A run carries at most 1 MB of images, counting earlier turns and what MCP tools return. Past that, the model sees the newest images that fit and a short note in place of each older one.

