Skip to main content
Glama
gmail-mcp
by gchallen

list_attachments

Read-only

Lists attachments on a Gmail message, including filename, MIME type, size, attachment ID, and inline-image status so you can identify files before reading or downloading them.

Instructions

List the attachments on a message: filename, MIME type, size, attachment ID, and whether it is an inline image.

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": {
      "messageId": "<messageId>"
    },
    "name": "list_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the concrete return shape, which is valuable given there is no output schema, but says nothing about pagination, empty results, attachment size limits, or whether inline images are included by default.

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?

One sentence, zero padding, front-loaded with the action and then the returned fields. Nothing in it is redundant with the name alone.

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 one-parameter read-only listing tool with annotations and no output schema, the definition is nearly sufficient: the agent knows what it gets back and that the call is safe. Gaps are minor — the messageId format and what happens with zero attachments or oversized payloads are unstated.

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 description coverage is 0% for the single required parameter, so the schema supplies only the name 'messageId' and its type. The description's phrase 'on a message' confirms the parameter identifies the target message but adds no format, ID-shape, or lookup guidance the agent could not already read from the schema.

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?

States a specific verb and resource ('List the attachments on a message') and enumerates exactly what comes back (filename, MIME type, size, attachment ID, inline-image flag). That is far more specific than the bare name, though it never names save_attachments as the adjacent operation.

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 explicit when-to-use or when-not-to-use guidance. The field list implicitly signals this is a metadata-only call (you would call it before save_attachments), but the agent must infer that, and no prerequisites or alternative tool is stated.

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