Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

drive_download_file

Downloads a Google Drive file to a local folder and exports Google Docs, Sheets, or Slides to formats such as PDF, DOCX, XLSX, CSV, PPTX, TXT, Markdown, or HTML.

Instructions

Download a Drive file to a local folder. Google Docs/Sheets/Slides are exported (format: pdf, docx, xlsx, csv, pptx, txt, md, html).

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>",
      "saveDir": "<saveDir>"
    },
    "name": "drive_download_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYes
formatNoExport format for Google-native files (default pdf)
saveDirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true. The description adds substantive behavior beyond them: Google-native files are exported (converted) rather than downloaded raw, and the allowed export formats are enumerated. It omits what happens on name collision/overwrite and whether the target folder must exist, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core action front-loaded and the export caveat immediately after. Tight and purposeful, though the parenthetical format list could have been pushed to the parameter entry.

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?

No output schema exists, so the description should state what comes back (e.g., the saved path or file name) and how collisions are handled for a tool that writes to the local filesystem; neither is covered. For a three-parameter download tool this leaves real gaps.

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 only 33%; only 'format' is documented there (default pdf). The description usefully clarifies that format applies only to Google Docs/Sheets/Slides and lists the valid values, but 'fileId' and 'saveDir' get no added meaning (path form, creation behavior, permissions).

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 Drive file to a local folder'. The word 'Download' plus the local-folder target implicitly separates it from read-style siblings like drive_read_file_text, though no sibling is named explicitly.

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 context is implied by 'to a local folder' versus reading text in-place, but there is no explicit when-to-use/when-not guidance and no mention of the alternative tools the agent might pick instead.

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