mcp-google-sheets

get_multiple_sheet_data

Read-only

Retrieve data from multiple ranges across Google Sheets in one request. Specify spreadsheet ID, sheet, and range for each query.

Instructions

Get data from multiple specific ranges in Google Spreadsheets.

Args: queries: A list of dictionaries, each specifying a query. Each dictionary should have 'spreadsheet_id', 'sheet', and 'range' keys. Example: [{'spreadsheet_id': 'abc', 'sheet': 'Sheet1', 'range': 'A1:B5'}, {'spreadsheet_id': 'xyz', 'sheet': 'Data', 'range': 'C1:C10'}]

Returns: A list of dictionaries, each containing the original query parameters and the fetched 'data' or an 'error'.

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": {
      "queries": "<queries>"
    },
    "name": "get_multiple_sheet_data"
  }
}

Input Schema

Name	Required	Description	Default
`queries`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.2Jun 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description explains the return format (list of dicts with original query and data or error), which adds behavioral detail beyond the readOnlyHint annotation. It discloses that the tool fetches data and can return errors per query. No contradictions 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.

Conciseness4/5

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

The description is concise, starting with the purpose and then detailing the parameters and return format in structured sections. There is slight redundancy (e.g., repeating 'A list of dictionaries'), but overall it is efficient and easy to parse.

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

Completeness5/5

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

Given the low complexity (single parameter, output schema present), the description covers all necessary aspects: purpose, parameter details with example, and return structure. No major gaps exist for an agent to correctly invoke the tool.

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

Parameters5/5

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

The input schema has 0% description coverage, but the description provides thorough parameter semantics: it specifies that 'queries' is a list of dicts with required keys 'spreadsheet_id', 'sheet', and 'range', and includes an example. This fully compensates for the schema's lack of descriptions.

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 'Get data from multiple specific ranges in Google Spreadsheets', using a specific verb 'Get' and resource 'multiple specific ranges'. This distinguishes it from sibling tools like get_sheet_data (single range) and get_multiple_spreadsheet_summary (summary of multiple spreadsheets). The purpose is unambiguous and well-differentiated.

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?

The description implies the tool is for multiple ranges but does not explicitly state when to use it over alternatives like get_sheet_data for single ranges. There is no mention of when not to use it or context for batching. The usage guidance is implicit rather than explicit.

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