Skip to main content
Glama
nabheet

google-services-mcp

by nabheet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Download Drive file

google_drive_download

Downloads a Drive file's raw bytes, returning decoded text for text files or base64 for binary files; optionally writes the bytes to a local path.

Instructions

Download a file's raw bytes (non-Google-native files). Text content returns decoded text; binary returns base64. Pass saveToPath to write bytes to a local file instead.

Input Schema

NameRequiredDescriptionDefault
fileIdYesDrive file ID.
accountNoAccount nickname to use.
saveToPathNoLocal path to write the raw bytes to (returns { savedTo }). Must be inside the save root: GOOGLE_MCP_SAVE_ROOT, default ~/Downloads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.95
    • changedInput schema / properties / saveToPath / description
      Previous value: -"Local path to write the raw bytes to (returns { savedTo } instead of data)."New value: +"Local path to write the raw bytes to (returns { savedTo }). Must be inside the save root: GOOGLE_MCP_SAVE_ROOT, default ~/Downloads."
  2. Changed1 schema field changedv0.1.60
    • addedInput schema / properties / saveToPath
      Added value: +{
+  "description": "Local path to write the raw bytes to (returns { savedTo } instead of data).",
+  "type": "string"
+}
  3. Addedv0.1.30

TDQS

A3.5/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 burden, and it does add real value by specifying the conditional return shape (decoded text vs. base64). However, it omits what happens when the file IS Google-native (error? empty?), whether saveToPath overwrites an existing file, and any size/permission constraints on large binaries.

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?

Three short sentences, front-loaded with the core action and scope, then the return-variant rule, then the optional output destination. Nothing is padded and each clause adds distinct information.

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 3-parameter tool with no output schema and no annotations, the description covers the primary return shapes but leaves the Google-native edge case, overwrite behavior, and size limits unstated. Adequate to invoke on the happy path, thin on failure modes.

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 100%, so fileId, account and saveToPath are already fully documented, including the save-root restriction. The description restates saveToPath's effect without adding constraints beyond the schema, so baseline 3 applies.

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 (download) and resource (a file's raw bytes), and narrows the scope with '(non-Google-native files)'. That scope carve-out implicitly separates it from google_drive_export, but the sibling is never named, so the agent must infer the boundary.

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 '(non-Google-native files)' parenthetical implies that Google-native docs belong elsewhere, and the saveToPath sentence gives one usage pattern, but neither is framed as an explicit when-to-use rule. There is no routing to google_drive_export for Docs/Sheets/Slides and no guidance on when returning bytes vs. writing to disk is preferred.

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