Skip to main content
Glama
gmail-mcp
by gchallen

get_draft

Read-only

Read a Gmail draft by its draft ID to retrieve recipients, subject, body, attachments, and a direct Gmail link.

Instructions

Read a draft by draft ID (not message ID): recipients, subject, body, attachments and a Gmail link.

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>"
    },
    "name": "get_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoWhich fields to return. "plain_text" (default): headers, snippet, labels, attachments list and the text body (HTML converted to text when there is no text part). "full": plain_text plus htmlBody. "minimal": headers, snippet and labels only, no body. "metadata": like minimal but without subject or snippet. "raw": the RFC 822 source.
draftIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that a Gmail link is returned and enumerates the payload contents, but says nothing about behavior when the draft ID is invalid/not found or whether attachments are inline references versus content.

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?

A single sentence that front-loads the identifier and its type caveat before listing the returned fields. No filler, no restating the tool name.

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?

With only two parameters, no output schema, and format fully described in the schema, the description's field enumeration adequately tells the agent what to expect back. Minor gaps: no error behavior for a missing draft and no note that body detail varies with the format parameter.

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

Parameters4/5

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

With 50% schema coverage, the description compensates for the undocumented draftId by clarifying it is a draft ID, not a message ID — a distinction the schema leaves ambiguous. The format parameter is already thoroughly documented in the schema, so no further explanation is needed.

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 ("Read a draft by draft ID") and lists exactly what comes back: recipients, subject, body, attachments, Gmail link. The parenthetical "(not message ID)" pre-empts confusion with the get_message sibling, so an agent can pick between them without opening either schema.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: it makes clear this is the draft-read path keyed on draft ID, which implicitly routes away from get_message. There is no explicit when-to-use/when-not guidance or named alternative (e.g. list_drafts to discover IDs, get_message for sent mail).

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