Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

gmail_download_attachment

Saves a Gmail attachment to a local directory or uploads it directly to a Google Drive folder.

Instructions

Download an email attachment to a local path, or save it straight into Google Drive.

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>",
      "attachmentId": "<attachmentId>",
      "filename": "<filename>"
    },
    "name": "gmail_download_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveDirNoLocal directory to save into
filenameYesFile name to save as (use the attachment's filename)
messageIdYes
attachmentIdYes
saveToDriveFolderIdNoDrive folder ID to upload into ('root' for My Drive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, and the description is consistent with a write-to-destination operation. It adds the useful behavioral fact that output can land either on local disk or in Drive, but says nothing about overwrite behavior, whether an existing file is replaced, or what is returned after the write.

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?

A single front-loaded sentence with zero filler; the alternative destinations are presented together in the order a caller needs to consider them.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter write-side tool with no output schema and only 60% schema coverage, the description leaves real gaps: default behavior when neither destination parameter is supplied, how messageId and attachmentId are obtained, and what the result looks like. It is adequate to start but not complete.

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 60%: saveDir, filename, and saveToDriveFolderId are documented, while messageId and attachmentId are not. The description's contribution is pairing the two destination modes with the corresponding destination parameters, which is meaningful but not detailed enough to fully compensate for the undocumented identifiers.

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 ('Download an email attachment') plus the two supported destinations (local path or Google Drive), which is more than a tautology. It does not explicitly distinguish itself from the sibling drive_download_file, which targets a different resource, so it falls short of a 5.

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

Usage Guidelines3/5

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

The 'or' phrasing implies two usage modes, giving some context for when a caller might pick this tool. However, it never states the condition that selects one mode over the other (saveDir vs saveToDriveFolderId), nor any prerequisites such as authentication or attachment availability.

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