Gmail Multi-Inbox MCP Server

search_drafts

Find Gmail drafts by query string and retrieve draft IDs, message IDs, thread IDs, subject, recipient, and snippet. Use when you need to send or delete a found draft.

Instructions

Search drafts by Gmail query string. Returns draft_id (for send_draft/delete_drafts), message_id, thread_id, subject, to, and snippet. Use instead of search_emails when you need to delete or send a found draft.

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": {
      "account": "<account>",
      "query": "<query>"
    },
    "name": "search_drafts"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Gmail search query (e.g. "to:bob@example.com" or "subject:follow up").
`account`	Yes	Account id.
`max_results`	No	Maximum number of results (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.2Aug 14, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses return fields and the workflow purpose (draft_id for send_draft/delete_drafts), adding useful context. However, it does not explicitly state that the operation is read-only, nor does it describe pagination or empty-result behavior. There is no contradiction, but transparency is incomplete.

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?

The description is two sentences, front-loaded with the primary action. The return fields and usage guidance are packed efficiently with no redundant information. Every sentence earns its place.

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 a tool with no output schema, the description lists all return fields and gives clear usage guidance. It covers the essentials for a search tool but omits details about sorting or error behavior. Overall, adequately complete for an agent to use correctly in most cases.

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?

Input schema coverage is 100%, with all three parameters documented. The description adds no parameter-specific information beyond what the schema already provides. Baseline of 3 applies because the schema handles the heavy lifting.

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 states 'Search drafts by Gmail query string' with a specific verb and resource. It lists return fields and explicitly distinguishes from sibling search_emails by saying 'Use instead of search_emails when you need to delete or send a found draft.'

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: 'Use instead of search_emails when you need to delete or send a found draft.' This clearly indicates an alternative tool and the condition for choosing this one, satisfying the when/when-not/alternatives criterion.

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

Deploy Server