Google Sheets and Drive MCP

Overview Schema Source Related Servers Discussions Admin

batch_read_ranges

Read multiple specified A1 ranges from a Google Sheet in a single API call, reducing request overhead and improving efficiency.

Instructions

Read several explicitly bounded A1 ranges in one API request.

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": {
      "spreadsheet_id": "<spreadsheet_id>",
      "ranges": "<ranges>"
    },
    "name": "batch_read_ranges"
  }
}

Input Schema

Name	Required	Default
`ranges`	Yes
`spreadsheet_id`	Yes
`major_dimension`	No	ROWS
`value_render_option`	No	FORMATTED_VALUE

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 28, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Minimal disclosure beyond 'one API request'; no mention of behavior like range ordering, limits, or error handling. No annotations provided to supplement.

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

Conciseness3/5

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

Single sentence, concise but omits critical details. Could be more structured to cover usage and parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (batch operation, multiple parameters, output schema), the description is insufficiently complete. Missing guidance on range format, options, and batching behavior.

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?

Only the 'ranges' parameter is described ('explicitly bounded A1 ranges'). Other parameters (spreadsheet_id, major_dimension, value_render_option) are not mentioned. With 0% schema coverage, the description should add more 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?

The description clearly states it reads multiple A1 ranges in one request, distinguishing it from read_range which reads a single range. However, it could be more explicit about the batch nature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like read_range; the batching benefit is implied but not stated explicitly.

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