email_draft_update
Update an existing email draft's recipients, subject, and body in place while keeping reply drafts in their thread. Use the returned draft ID, since IMAP providers replace the draft.
Instructions
Update an existing email draft in place (to/subject/body). A reply draft stays in its thread. On Gmail and Outlook the draft id is unchanged. On iCloud/generic IMAP there is no in-place update (the old draft is deleted and a new one appended), so the returned id is a NEW id and the old one no longer resolves; always use the id this call returns, not the one you passed in.
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>",
"draftId": "<draftId>",
"to": "<to>",
"subject": "<subject>",
"body": "<body>"
},
"name": "email_draft_update"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | ||
| body | Yes | ||
| draftId | Yes | ||
| subject | Yes | ||
| accountId | Yes | ||
| signature | No | Add the account's signature (default true), as on email_draft_create. The body given here replaces the draft's body, so the signature is added to it once; a body that already holds one (passed back from the draft) is left alone, so repeated updates never stack a second one | |
| attachments | No | Files to attach. When given, they replace the draft's current attachments; an empty list removes them all. When omitted, the draft keeps the files it has. | |
| sourceFolder | No | Source folder (required for IMAP/iCloud when the draft is not in the default Drafts folder) |