email_draft_create
Create a new email draft with recipients, subject, body, and attachments; optionally save it as a reply in an existing message thread.
Instructions
Create a new email draft. Pass inReplyToEmailId to save it as a reply in that message's thread
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>",
"to": "<to>",
"subject": "<subject>",
"body": "<body>"
},
"name": "email_draft_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | ||
| body | Yes | ||
| subject | Yes | ||
| 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 | |
| inReplyToEmailId | No | Id of the email this draft replies to. The draft joins that thread (Gmail threadId, Outlook createReply, In-Reply-To/References headers elsewhere) | |
| inReplyToSourceFolder | No | Folder of the email named in inReplyToEmailId (required for IMAP/iCloud when that email is not in INBOX). The draft itself is saved to Drafts |