google-workspace-mcp

drive_read_file

Extract text from Google Drive files: read contents of Docs, Sheets, Slides exports, or raw text files.

Instructions

Read the text content of a Drive file (Google Docs/Sheets/Slides exported, or raw text files).

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_read_file"
  }
}

Input Schema

Name	Required	Description	Default
`file_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose that Google Docs/Sheets/Slides are exported and that raw text files are read directly, which adds useful behavioral context. However, it does not mention limitations (e.g., unsupported binary formats like PDFs) or any error behavior, which is a notable gap for a read tool.

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 a single, concise sentence that front-loads the primary action and scope. Every word is functional, with no fluff or repetition.

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 tool with only one parameter and an output schema present, the description adequately covers the core functionality. It explains the input (a Drive file) and the output (text content). It lacks detail on edge cases like unsupported file types, but overall it is sufficiently complete for a simple read operation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It neither explains what 'file_id' refers to nor provides examples or format hints. While the parameter name is self-explanatory, the description adds no specific meaning beyond the schema's 'string' type, leaving ambiguity about where to obtain a valid ID.

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 uses a specific verb ('Read') and resource ('text content of a Drive file'), and clearly specifies the scope: Google Docs/Sheets/Slides exported, or raw text files. This distinguishes it from sibling tools like drive_export (which exports files) and drive_copy_file (which 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 clear context on when to use the tool (when you need the text content of a Drive file), and it disambiguates from file export or copying. However, it does not explicitly state when not to use it or mention alternatives, so it falls short of a 5.

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

Deploy Server