Update a draft
update_draftReplace a Gmail draft's entire content by supplying the complete new message state: recipients, subject, body, and reply headers. Read the draft first because missing fields are dropped, not kept.
Instructions
REPLACES a draft's entire message — the Gmail API has no partial draft edit, so omitted fields are dropped, not kept. Read the current content with get_draft first, then pass the complete new state (recipients, subject, body, and thread_id/in_reply_to for reply drafts). The draft id stays the same; the underlying message id changes. Returns the updated draft.
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": {
"draft_id": "<draft_id>"
},
"name": "update_draft"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cc | No | Carbon-copy recipients. | |
| to | No | Primary recipients (optional for a draft). | |
| bcc | No | Blind-copy recipients. | |
| subject | No | The subject line. | |
| draft_id | Yes | The draft id from list_drafts or create_draft output. | |
| body_html | No | HTML body (multipart/alternative when body_text is also set). | |
| body_text | No | Plain-text body. | |
| thread_id | No | Make it a reply draft in this thread (pair with in_reply_to and a matching subject). | |
| references | No | Explicit References header chain (defaults to in_reply_to). | |
| in_reply_to | No | RFC Message-ID of the message being replied to (headers.messageId from get_message). |