Skip to main content
Glama
Sign In
google-workspace-mcp

google-workspace-mcp

by smk-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gmail_drafts_list

List Gmail drafts for a specified account, optionally filtering with standard Gmail search syntax and limiting results. Use it to find saved draft messages without opening each one.

Instructions

List drafts. query uses standard Gmail search syntax.

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": "gmail_drafts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
accountYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavior. It only states 'List drafts' without explaining output format, pagination, rate limits, or any side effects. This is minimal for a read operation.

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?

Extremely concise with two sentences. Front-loaded with the primary action. No extraneous information.

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?

Given three parameters, one required, and no output schema, the description fails to provide enough context for the agent to correctly invoke the tool. Missing details on return structure, pagination behavior, and account usage.

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%, so the description must compensate. It adds meaning only for 'query' by mentioning Gmail search syntax. 'account' and 'max_results' receive no explanation, leaving the agent to infer their roles.

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 clearly states 'List drafts' with a specific verb and resource. It is distinct from siblings like gmail_search (which targets messages) and other draft operations. The addition of query syntax reference adds specificity.

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 on when to use this tool versus alternatives like gmail_search for messages or gmail_draft_create. The description does not mention when not to use it or prerequisites.

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