Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

gmail_list_drafts

Read-only

List Gmail drafts to review, edit, or send saved messages, with an optional result limit.

Instructions

List email drafts.

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

Input Schema

NameRequiredDescriptionDefault
maxResultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no indication of whether results are paginated, whether drafts are returned with full bodies or only IDs/snippets, or whether a page token exists. For a list tool this is a meaningful gap.

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?

The description is a single front-loaded sentence with zero wasted words. It is efficient, though its brevity is closer to under-specification than to disciplined conciseness.

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?

With no output schema and no annotation-level detail about return values, the description should say what a draft listing contains (IDs, snippets, timestamps) and how maxResults interacts with retrieval. Neither is present, so an agent knows what the tool does but not what it gets back.

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%, and the single parameter maxResults is never mentioned in the description. The schema does supply a default (20) and a range (1–100), so an agent can still call the tool, but the description contributes no meaning and does not explain the absence of paging/filtering options.

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 states a specific verb ("List") and resource ("email drafts"), which makes the operation immediately identifiable and clearly distinct from mutation siblings like gmail_create_draft or gmail_send_draft. It stops short of a 5 because it does not contrast itself with other read siblings such as gmail_search or gmail_read_message.

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?

There is no guidance on when to use this tool versus alternatives — nothing says to prefer gmail_search when looking for a draft by content, or gmail_read_message for full draft bodies. The agent must infer usage entirely from the name.

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