mcp-google-sheets-server

sheets_list_charts

Lists all charts in a specified Google Sheets spreadsheet, returning their details.

Instructions

List all charts in a spreadsheet with their details

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>"
    },
    "name": "sheets_list_charts"
  }
}

Input Schema

Name	Required	Description	Default
`spreadsheetId`	Yes	The ID of the spreadsheet

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Sep 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The description implies a read-only operation by using 'List', but it does not explicitly state side effects or lack thereof. Since there are no annotations to rely on, the description alone partially covers behavioral transparency but leaves room for interpretation about what 'details' entails.

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 with no unnecessary words. It is front-loaded with the action and resource, making it easy to parse quickly.

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 description adequately conveys the tool's purpose for the given complexity. While it does not specify the structure of the 'details' returned, this is not critical given the simple read-only nature and the availability of the tool name. The context is sufficiently complete for an agent to decide when to use it.

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 only parameter, spreadsheetId, is well-described with 'The ID of the spreadsheet'. The schema provides full coverage, and the description adds no ambiguity. Both the schema and description align perfectly.

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 the tool's function: to list all charts in a spreadsheet and provide their details. The verb 'List' and the resource 'charts' are specific, and the scope 'in a spreadsheet' is unambiguous. It is easily distinguished from sibling chart tools that create or update charts.

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 does not explicitly mention when to use this tool versus alternatives such as creating or updating charts. While the listing nature implies a read-only use case, there is no direct guidance on when to choose this over other chart-related tools.

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