outlook__add_attachment_to_message
Access
Requires a project integration connection for outlook.
Call type: Can change resources.
Arguments
Example request
Send this JSON-RPC request through an initialized MCP client. Replace sample identifiers and values before calling the tool. See MCP client setup.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "outlook__add_attachment_to_message",
"arguments": {
"messageId": "example",
"name": "example",
"contentBytes": "example"
}
}
}Result
No output schema is published for this tool. The input contract does not define its return fields. Inspect the MCP response content and isError; do not assume a fixed object shape. See the outlook integration reference for provider setup and tool context.
Full schemas
{
"type": "object",
"properties": {
"messageId": {
"type": "string",
"description": "Draft message ID"
},
"@odata.type": {
"type": "string",
"description": "Microsoft Graph attachment type"
},
"name": {
"type": "string",
"description": "Attachment filename"
},
"contentBytes": {
"type": "string",
"description": "Base64-encoded attachment content. The decoded attachment must be under 3 MB. Larger files require an upload session, which this connector does not expose."
},
"contentType": {
"type": "string",
"description": "Attachment MIME type"
},
"isInline": {
"type": "boolean",
"description": "Whether the attachment is inline"
}
},
"required": [
"messageId",
"name",
"contentBytes"
],
"description": "Arguments for the outlook__add_attachment_to_message tool."
}