google-workspace-mcp-server

Get Google Spreadsheet

sheets_get_spreadsheet

Read-onlyIdempotent

Retrieve metadata and optional cell data from a Google Spreadsheet. Get title, sheet names, row/column counts, locale, and URL.

Instructions

Retrieve metadata and optionally cell data from a Google Spreadsheet.

Args:

spreadsheet_id (string): The ID of the Google Spreadsheet (found in the URL after /d/)
include_grid_data (boolean): Whether to include cell data (default: false)
response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Spreadsheet title, sheets info, and metadata. For JSON format: { "spreadsheetId": string, "title": string, "locale": string, "sheets": [{ "sheetId": number, "title": string, "rowCount": number, "columnCount": number }], "spreadsheetUrl": string }

Examples:

Get spreadsheet info: spreadsheet_id="1BxiMVs0XRA5nFMdKvBdBZjgmUUqptlbs74OgvE2upms"

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

Input Schema

Name	Required	Description	Default
`spreadsheet_id`	Yes	The ID of the Google Spreadsheet (found in the URL)
`include_grid_data`	No	Whether to include cell data (can be large)
`response_format`	No	Output format: 'markdown' for human-readable or 'json' for structured data	markdown

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.3May 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds context beyond annotations by warning that include_grid_data 'can be large' and detailing the exact JSON return structure, which is valuable for an agent.

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?

Well-structured with Args, Returns, and Examples. The purpose is front-loaded. It is slightly long but every section contributes meaningful information, with no fluff.

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?

For a read-only get tool, it provides a detailed return format and example. The main gap is the lack of explicit comparison to sheets_get_values, but the description still covers the core functionality and edge cases (large grid data).

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?

Schema description coverage is 100%, so baseline is 3. The description adds extra value: for spreadsheet_id it specifies 'found in the URL after /d/', and for include_grid_data it warns 'can be large', both beyond the schema 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?

Specific verb 'retrieve' with resource 'Google Spreadsheet' and clarifies it can optionally include cell data. Distinguishes from siblings like sheets_get_values (which focuses on values) and docs_get_document (different resource).

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?

Does not explicitly name alternatives or when-to-use. The phrase 'optionally cell data' implies that for pure cell data, sheets_get_values might be more appropriate, but this is not stated. Lacks explicit exclusions.

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