gmail-attachments-mcp

download_attachment

Save a Gmail attachment to disk and return the saved file path. Select the message ID, filename, optional duplicate index, and destination folder; existing files are not overwritten.

Instructions

Save one attachment to disk and return the file path.

filename: exact name from list_attachments. index: pick among duplicate names.
dest_dir: folder to save into (default ~/Downloads/gmail-attachments).
Existing files are never overwritten; a numeric suffix is added.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`index`	No
`dest_dir`	No
`filename`	Yes
`message_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does add real value: existing files are never overwritten and a numeric suffix is added on collision. It does not cover error behavior (missing attachment, bad index), permissions/auth needs, or any rate limits, so significant disclosure 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 primary action is front-loaded in the first sentence, then parameters follow in tight, labeled lines. Every sentence carries information (workflow source, disambiguation, default path, overwrite policy) with no filler.

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?

An output schema exists, so the return value need not be elaborated beyond the stated file path. For a 4-parameter, no-annotation tool the description covers the practically important behavior, with the only clear hole being message_id semantics and error handling.

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 0%, so the description is the only source of parameter meaning. It documents filename (exact name from list_attachments), index (duplicate disambiguation), and dest_dir (default and purpose), which is genuinely useful, but the required message_id parameter is never explained in the description or schema.

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?

States a specific verb and resource ('Save one attachment to disk and return the file path') and makes the single-attachment scope explicit. The disk-saving framing implicitly separates it from read_attachment_text, and it names list_attachments as the filename source, so an agent can place it correctly among siblings.

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

Usage Guidelines4/5

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

'filename: exact name from list_attachments' and 'index: pick among duplicate names' establish the intended call sequence and the disambiguation case for duplicates. It gives clear context for how to invoke but never states when NOT to use this tool or when read_attachment_text is preferable.

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

Deploy Server