mcp-template

gmail_composer.save_draft

Saves changes to an existing Gmail draft by persisting current composer fields, including recipients, subject, body, and attachments.

Instructions

Persist the current composer fields onto an existing Gmail draft.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cc`	No
`to`	No
`bcc`	No
`body`	No
`subject`	No
`user_id`	No
`draft_id`	Yes
`attachments`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`cc`	No
`to`	No
`bcc`	No
`body`	No
`subject`	No
`draft_id`	Yes
`thread_id`	No
`attachments`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 19, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations exist, and the description only says 'persist' without explaining behavioral traits like overwrite behavior, auth requirements, or side effects.

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?

Single sentence is concise and front-loaded, but could benefit from more detail without significant bloat.

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

Completeness1/5

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

Despite having an output schema, the description lacks context on return values, errors, or any additional behavioral detail needed given 8 parameters and no annotations.

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

Parameters1/5

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

Schema description coverage is 0%, and description adds no explanation for any of the 8 parameters beyond their names.

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?

Description clearly states the action ('persist') and resource ('current composer fields onto an existing Gmail draft'), distinguishing it from sibling tools like send or discard.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives (e.g., save_draft vs send), or when not to use it.

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

Deploy Server