Skip to main content
Glama

update_draft

Replace an existing Gmail draft's body, recipients, subject, and attachments without sending it; thread and reply headers stay intact, and unchanged fields remain as they are.

Instructions

Replace the text of an existing draft, without sending it; thread and reply headers (In-Reply-To) are kept.

Empty to, subject, cc, bcc = unchanged. Attachments already there are kept, except those named in removeAttachments; attachments adds more (same rules as create_draft). The HTML version of a draft written in Gmail is replaced by the plain text.

Args: draftId: draft ID (returned by create_draft or list_drafts). body: the new complete body, plain text. to: new recipients, or empty to keep them. subject: new subject, or empty to keep it. cc: new carbon copy, or empty to keep it. bcc: new blind carbon copy, or empty to keep it. attachments: absolute paths of files to add, optional. removeAttachments: exact names of attachments to remove, optional.

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": {
      "draftId": "<draftId>",
      "body": "<body>"
    },
    "name": "update_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toNo
bccNo
bodyYes
draftIdYes
subjectNo
attachmentsNo
removeAttachmentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.3
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "update_draftOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description adds genuinely non-obvious behavior: In-Reply-To/thread headers survive, empty fields mean "keep existing," existing attachments persist unless explicitly named in removeAttachments, and the Gmail HTML version is replaced by plain text. That last point is a real data-loss disclosure an agent could not infer from annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening paragraph is front-loaded with the highest-value facts (no send, headers preserved, HTML replacement). The Args block is mostly additive, though "to: new recipients, or empty to keep them" restates the earlier blanket "Empty ... = unchanged" rule for each of four fields, which is mild redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter mutation tool with no output schema and zero annotation detail, the description covers behavior, side effects, and all parameter semantics. It doesn't say what is returned or what happens on a bad draftId / permission failure, but those are secondary for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the full burden, and it does: every one of the 8 parameters is explained, including the crucial "empty to/subject/cc/bcc = unchanged" convention, absolute-path requirement for attachments, and exact-name matching for removeAttachments. This is meaning the schema's bare types and defaults cannot convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Replace the text of an existing draft") and immediately scopes it against the obvious sibling risk by saying "without sending it," which separates it from send_draft. It also clarifies that thread/reply headers are preserved, so an agent knows this is an in-place edit rather than a new message.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear lifecycle context by noting draftId is "returned by create_draft or list_drafts" and that attachment rules mirror create_draft, which routes the agent to the right siblings for setup. It lacks an explicit "use X instead when..." exclusion (e.g. versus create_draft for brand-new drafts), so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.