email_reply
Reply to an existing email within its thread, optionally to all original recipients or custom To/Cc/Bcc. Add attachments, a signature, or extra recipients across Gmail, Outlook, iCloud, and IMAP.
Instructions
Reply to an existing email, in its thread. With replyAll the reply goes to the original sender and all To and Cc recipients, except the account's own address
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"accountId": "<accountId>",
"emailId": "<emailId>",
"body": "<body>"
},
"name": "email_reply"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cc | No | Cc recipients. Replaces any Cc carried over by replyAll | |
| to | No | Replace the default To (the original sender). Use it when the original was sent by you, so the reply goes to the real correspondents instead of back to yourself | |
| bcc | No | ||
| body | Yes | ||
| emailId | Yes | ||
| replyAll | No | ||
| accountId | Yes | ||
| signature | No | Add the account's signature (default true). Gmail: the signature of the send-as address the mail goes out from, read from Gmail's settings, in Gmail's own markup above any quoted history; a body that already holds one is left alone. Outlook.com, iCloud and IMAP have no signature a client can read, so nothing is added there. The result's `signature` field says what happened | |
| attachments | No | Files to attach, at most 100. Total size is capped at 25 MB | |
| sourceFolder | No | Source folder (required for IMAP/iCloud when email is not in INBOX) | |
| additionalRecipients | No | Extra To recipients added to the default or given To (deduplicated by address) |