mcp-google-sheets-server

sheets_get_data

Retrieve data from Google Sheets by specifying spreadsheet ID and range, with optional formatting and date rendering controls.

Instructions

Get data from Google Sheets with optional formatting

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": {
      "spreadsheetId": "<spreadsheetId>",
      "range": "<range>"
    },
    "name": "sheets_get_data"
  }
}

Input Schema

Name	Required	Description	Default
`range`	Yes	The range to retrieve (e.g., A1:C10)
`spreadsheetId`	Yes	The ID of the spreadsheet
`valueRenderOption`	No	How values should be rendered	FORMATTED_VALUE
`dateTimeRenderOption`	No	How dates should be rendered	FORMATTED_STRING

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Sep 7, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries full burden for disclosing behavior. It does not mention that this is a read-only operation, that it does not modify data, or any other side effects or guarantees.

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 efficiently conveys the core purpose without unnecessary words or redundancy.

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?

The operation is simple and the schema covers all parameters, but the lack of usage guidance and behavioral transparency leaves gaps. An agent might not know when to prefer this over other get operations or that it is safe (read-only).

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?

The schema provides full descriptions for all four parameters, including enums. The phrase 'optional formatting' adds a minor hint about valueRenderOption and dateTimeRenderOption but does not materially enhance the schema's explanations.

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 gets data from Google Sheets, which is a specific verb and resource. It doesn't explicitly distinguish itself from sibling tools like sheets_batch_get or sheets_get_metadata, but the name and phrasing make its purpose reasonably clear.

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 is provided on when to use this tool versus alternatives such as sheets_batch_get or sheets_get_metadata. Users are left to infer from the name alone.

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