Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

drive_files_download

Read-only

Download a Google Drive file's content as text or base64, export Docs, Sheets, and Slides to readable formats, and save binary files like images or PDFs to a local path.

Instructions

Download a file's content from Google Drive. Returns the text content for text files, or a base64-encoded string for binary files. For Google Docs/Sheets/Slides, exports to a readable format (plain text by default).

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": {
      "fileId": "<fileId>"
    },
    "name": "drive_files_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesThe file ID to download
savePathNoFor binary files (images, PDFs): save to this local path instead of returning content inline. Must be inside the server's file root (--file-root, default its working directory); a relative path resolves against the root. The file path is returned in the response.
exportMimeTypeNoFor Google-native files (Docs/Sheets/Slides): export format. Defaults to text/plain for Docs, text/csv for Sheets. Examples: text/plain, text/csv, application/pdf

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / savePath / description
      Previous value: -"For binary files (images, PDFs): save to this local path instead of returning content inline. The file path is returned in the response."New value: +"For binary files (images, PDFs): save to this local path instead of returning content inline. Must be inside the server's file root (--file-root, default its working directory); a relative path resolves against the root. The file path is returned in the response."
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavior beyond that: the default export format for Google-native files and the fact that content is returned as text or base64 depending on file type.

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: purpose first, then return behavior, then the Google-native special case. Nothing is redundant or padded.

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?

With no output schema, the description carries the burden of explaining return values and does so for all three branches (text, base64, exported format). It leaves out how it differs from drive_files_export and any size or error caveats, which are minor but real gaps for a download tool.

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 100%, so all three parameters are already well documented, including savePath root constraints and exportMimeType defaults. The description's mention of "plain text by default" largely restates the schema rather than adding new meaning.

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 a file's content from Google Drive") and clarifies what is returned for text vs binary files. It does not, however, differentiate itself from the sibling drive_files_export, even though it describes export behavior for Google-native files.

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?

Usage is implied by the format branches (text inline, binary base64 or savePath, Google-native exported), which effectively tells the agent when each behavior applies. There is no explicit when-to-use vs drive_files_export or drive_files_get, and no stated exclusions or prerequisites.

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