google-workspace-mcp-server

Get File Content

drive_get_file

Read-onlyIdempotent

Download a file from Google Drive by providing its file ID. Returns binary content for PDFs, images, and other files.

Instructions

Download and return the content of a file from Google Drive. Supports PDFs, images, and other binary files.

Args:

file_id (string): The ID of the file to download (found in the URL after /d/)

Returns: The file content. For PDFs and images, returns the binary content that Claude can read directly.

Examples:

Get PDF: file_id="1Q3BmlH3_sII1VGf0-GYXSiLGTZstM-l1"
From URL https://drive.google.com/file/d/ABC123/view -> file_id="ABC123"

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": {
      "file_id": "<file_id>"
    },
    "name": "drive_get_file"
  }
}

Input Schema

Name	Required	Description	Default
`file_id`	Yes	The ID of the file to download (found in the URL)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.3May 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare this as readOnly and idempotent per the hints. The description adds behavioral detail beyond those hints by specifying supported file types (PDFs, images, binary) and that binary content is returned so Claude can read it directly. No contradiction with annotations.

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 well-organized with clear Args, Returns, and Examples sections. It is concise, front-loads the main purpose in the first sentence, and every part serves a purpose without redundancy.

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?

For a single-parameter read-only tool, the description sufficiently covers purpose, input format, and return value. It misses minor details like error handling or behavior for text files, but these are not critical given the tool's simplicity and the strong annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already covers file_id with 100% description coverage. The description adds practical value by explaining how to extract the file_id from a URL (after /d/) and provides a concrete example, which goes beyond the schema's basic description.

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 clearly states the action ('Download and return the content of a file') and the resource ('Google Drive'). It distinguishes itself from sibling tools like drive_list_files or drive_copy_file by specifying that it retrieves file content, not metadata or copies.

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 a clear context for when to use the tool (when you need the actual file content) and includes examples for extracting file_id from URLs. It doesn't explicitly mention exclusions or alternatives, but the purpose is obvious enough for the agent to select it correctly.

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