Skip to main content
Glama

gmail create draft

gmail_create_draft

Creates a Gmail draft with recipients, subject, and body so messages can be reviewed before sending.

Instructions

Create a Gmail draft. Preferred over sending: nothing leaves the mailbox.

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": {
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "gmail_create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
bodyYes
htmlNo
subjectYes
thread_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=false, destructiveHint=false and openWorldHint=true. The description adds one genuinely useful behavioral fact beyond them: the draft stays inside the mailbox and is not delivered. It does not mention that repeated calls create duplicate drafts (idempotentHint=false) or where drafts become visible.

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

Conciseness5/5

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

Two short sentences, action stated first and the key rationale second, with no filler whatsoever.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but a 7-parameter mutation tool with 0% schema coverage needs more than twelve words. The absence of any parameter or threading guidance leaves an agent under-informed for anything beyond the simplest draft.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, so the description must compensate and it says nothing about any of them. Semantics for thread_id (reply threading), html (body interpretation), and cc/bcc are entirely left to field titles, which is a meaningful gap.

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

Purpose4/5

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

"Create a Gmail draft" is a specific verb+resource, and "Preferred over sending: nothing leaves the mailbox" implicitly contrasts it with the send path in the sibling list. The contrast is clear in meaning though it never names gmail_send_email as the alternative tool.

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?

It gives an explicit preference rule: use this rather than sending, because nothing is dispatched. That is real when-to-use guidance, but there is no instruction on how to use it for replies (thread_id) or any statement about when a draft is not appropriate.

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