Documentation Index
Fetch the complete documentation index at: https://agentclientprotocol.com/llms.txt Use this file to discover all available pages before exploring further.
Content
Understanding content blocks in the Agent Client Protocol
Content blocks represent displayable information that flows through the Agent Client Protocol. They provide a structured way to handle various types of user-facing content—whether it’s text from language models, images for analysis, or embedded resources for context.
Content blocks appear in:
- User prompts sent via
session/prompt - Language model output streamed through
session/updatenotifications - Progress updates and results from tool calls
Content Types
The Agent Client Protocol uses the same ContentBlock structure as the Model Context Protocol (MCP).
This design choice enables Agents to seamlessly forward content from MCP tool outputs without transformation.
Text Content
Plain text messages form the foundation of most interactions.
{
"type": "text",
"text": "What's the weather like today?"
}
All Agents MUST support text content blocks when included in prompts.
Image Content
Images can be included for visual context or analysis.
{
"type": "image",
"mimeType": "image/png",
"data": "iVBORw0KGgoAAAANSUhEUgAAAAEAAAAB..."
}
image prompt
capability when included in
prompts.
Audio Content
Audio data for transcription or analysis.
{
"type": "audio",
"mimeType": "audio/wav",
"data": "UklGRiQAAABXQVZFZm10IBAAAAABAAEAQB8AAAB..."
}
audio prompt
capability when included in
prompts.
Embedded Resource
Complete resource contents embedded directly in the message.
{
"type": "resource",
"resource": {
"uri": "file:///home/user/script.py",
"mimeType": "text/x-python",
"text": "def hello():\n print('Hello, world!')"
}
}
This is the preferred way to include context in prompts, such as when using @-mentions to reference files or other resources.
By embedding the content directly in the request, Clients can include context from sources that the Agent may not have direct access to.
embeddedContext prompt
capability when included in
prompts.
<ParamField path="text" type="string" required>
The text content of the resource
</ParamField>
<ParamField path="mimeType" type="string">
Optional MIME type of the text content
</ParamField> <ParamField path="blob" type="string" required>
Base64-encoded binary data
</ParamField>
<ParamField path="mimeType" type="string">
Optional MIME type of the blob
</ParamField> Resource Link
References to resources that the Agent can access.
{
"type": "resource_link",
"uri": "file:///home/user/document.pdf",
"name": "document.pdf",
"mimeType": "application/pdf",
"size": 1024000
}Last updated Oct 08, 2026