Skip to main content
Glama
Sign In
gmail-mcp

gmail-mcp

by cunicopia-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_drafts

Retrieve draft email IDs from a Gmail account. Specify the account and optionally set a maximum number of results to get a list of drafts for review or further processing.

Instructions

List draft messages in the account (returns draft ids).

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

Input Schema

NameRequiredDescriptionDefault
accountYesEmail address of the authorized Gmail account to act on.
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only adds that draft ids are returned, but omits behavioral details such as auth requirements, pagination behavior, sorting, and whether full message content is excluded. Some useful info is present, but significant gaps remain.

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 a single concise sentence that clearly states the action and the return value. It is appropriately sized and front-loaded, with no wasted words.

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

Completeness3/5

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

The tool is relatively simple, but the description lacks guidance on max_results semantics and does not leverage sibling distinctions. It provides the core purpose and return shape, which is minimally adequate, but leaves an agent without enough context for confident invocation.

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 only 50%; the account parameter is documented in the schema, but max_results is not described anywhere. The description does not compensate for this gap by explaining what max_results controls or how it affects results.

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?

The description uses a specific verb and resource: 'List draft messages' and notes the return value is draft ids. It is clear and distinct from the sibling tools, though it does not explicitly differentiate itself from similar listing/searching tools.

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 is provided about when to use this tool versus alternatives like search_messages or read_message. The intended context is only implied by the name and description, with no exclusions or alternative routing.

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

Deploy Server

Other Tools