Skip to main content
Glama
gmail-mcp
by gchallen

list_drafts

Read-only

Retrieve Gmail drafts newest first with IDs, filter them using Gmail search syntax, and optionally include full plain-text bodies for review.

Instructions

List drafts, newest first, with draft IDs. Filter with a Gmail query. view "full" adds bodies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNo"metadata" (default): headers and snippet. "full": also the plain-text body.
queryNoGmail search syntax, exactly as in the Gmail search box. Operators: from:, to:, cc:, bcc:, subject:, label:NAME, in:(inbox|sent|drafts|trash|spam|anywhere|archive), is:(unread|read|starred|important), has:attachment, filename:pdf, after:YYYY/MM/DD, before:YYYY/MM/DD, newer_than:7d, older_than:1y, larger:10M, "exact phrase", OR, -negation, ( ) grouping, {a b} for OR. Whitespace is AND. Keep queries keyword-based rather than pasting whole subjects.
pageTokenNo
maxResultsNoDefault 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A3.5/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 safety is covered. The description adds useful behavior (results are sorted newest first, draft IDs are returned, view=full yields bodies), but says nothing about pagination despite a pageToken parameter.

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?

Three short, front-loaded sentences with no filler. Minor redundancy in repeating the view=full body behavior already in the schema keeps it from a 5.

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?

A low-complexity read-only list tool with no output schema, so the description needn't explain return values in depth. Coverage of ordering, IDs, and filtering is adequate; only pagination behavior is unaddressed.

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

Parameters3/5

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

Schema coverage is 75%, and the schema already documents query syntax, view modes, and the maxResults default. The description's "Filter with a Gmail query" and "view full adds bodies" largely restate schema content rather than adding meaning, and pageToken remains undocumented in both.

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?

States a specific verb and resource ("List drafts") plus ordering ("newest first") and a distinguishing output detail (draft IDs returned). It does not explicitly contrast with get_draft or search_threads, so the boundary with siblings is only implicit.

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?

"Filter with a Gmail query" hints at the intended filtering flow, but there is no explicit when-to-use or when-not-to-use guidance, and no pointer to get_draft when a full draft body is needed.

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