Gmail Multi-Inbox MCP Server

sheets_read

Read cell values from a specified Google Sheets range, like 'Sheet1!A1:D10', using A1 notation to retrieve data from any sheet or the first sheet.

Instructions

Read cell values from a Google Sheet range (e.g., "Sheet1!A1:D10" or "A1:D10" for the first sheet).

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": {
      "account": "<account>",
      "spreadsheet_id": "<spreadsheet_id>",
      "range": "<range>"
    },
    "name": "sheets_read"
  }
}

Input Schema

Name	Required	Description
`range`	Yes	A1 notation range, e.g. "Sheet1!A1:D10".
`account`	Yes	Account id.
`spreadsheet_id`	Yes	Spreadsheet ID.
`value_render_option`	No	How values are rendered (default FORMATTED_VALUE).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.2Aug 14, 2026

TDQS

A3.6/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It implies a read-only operation but does not mention response format, error handling, authentication needs, or any side effects. The only extra detail is that 'A1:D10' refers to the first sheet, which is more parameter semantics than behavior.

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, well-structured sentence that immediately states the tool's purpose, includes helpful examples, and contains no filler or redundant information.

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?

The tool is simple with only four parameters, and the schema covers all of them. The description clearly explains the core action and range notation. However, it lacks any mention of return values or usage context, but given the simplicity and richness of the schema, it is mostly complete.

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 describes all parameters with 100% coverage, so baseline is 3. The description adds extra meaning for the 'range' parameter by explicitly stating that 'A1:D10' targets the first sheet, which is not fully explicit in the schema's example. This provides value beyond the schema.

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?

Description clearly states the tool reads cell values from a Google Sheet range, with a specific verb ('Read') and resource ('cell values from a Google Sheet range'). It also provides concrete examples of range notation, making the purpose unambiguous.

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?

The description provides no guidance on when to use this tool versus alternatives like sheets_write or sheets_append, nor does it mention any exclusions or prerequisites. It simply states the action without context.

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

Deploy Server