Skip to main content
Glama
Sign In
MCP Google Multi-Account Server

MCP Google Multi-Account Server

by bkbaheti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gmail_bulk_save_attachments

Download attachments from multiple Gmail messages to a local folder, returning a manifest of saved files. Uses readonly access.

Instructions

Download all attachments from one or more Gmail messages to a local directory. Returns a manifest of saved files. Requires readonly scope.

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": {
      "accountId": "<accountId>",
      "messageIds": "<messageIds>",
      "outputDir": "<outputDir>"
    },
    "name": "gmail_bulk_save_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdYesThe Google account ID, alias, or email
outputDirYesLocal directory path to save attachments to (will be created if needed)
messageIdsYesArray of message IDs to download attachments from
filenamePrefixNoOptional prefix for filenames. If not set, files use their original names with message ID prefix to avoid collisions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

A4.2/5.0
Behavior4/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 explicitly states the readonly scope requirement (auth need) and that it returns a manifest of saved files (output). This adds meaningful context beyond the tool name and schema, though it does not detail potential side effects like overwriting or long-running operations. The disclosure is solid for a straightforward download tool.

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 three sentences long, with the primary action front-loaded. Every sentence adds value: the action, the return value, and the required scope. No redundant or extraneous information is present.

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?

The description covers the core purpose, the return manifest, and the auth requirement. Given the tool's moderate complexity and full schema coverage, it is mostly complete. It does not describe the manifest contents or error handling, but these are not critical for the agent to invoke the tool correctly. The lack of an output schema makes the return-value mention particularly useful.

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?

The input schema covers 100% of the four parameters with clear descriptions. The tool description does not add any parameter-specific semantics beyond what the schema already provides, so the baseline of 3 applies.

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?

The description uses a specific verb ('Download') and clearly identifies the resource ('all attachments from one or more Gmail messages') and destination ('local directory'). This distinguishes it from sibling tools like gmail_get_attachment (single attachment) and gmail_list_attachments (listing only), making the tool's unique purpose immediately clear.

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?

The description provides clear context for when to use this tool: for downloading all attachments from one or more messages in bulk. It implicitly contrasts with single-attachment retrieval tools but does not explicitly name alternatives or state when not to use it. This is clear context without exclusions, aligning with a score of 4.

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