Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Read Sheet Values

read_sheet_values

Read-onlyIdempotent

Reads values from a specified Google Sheets range, returning each row with its row number and cells separated by tabs.

Instructions

Reads values from a specific range in a Google Sheet, one line per row: the sheet row number, then the row's cells separated by tabs.

Input Schema

Name	Required	Description	Default
`range_name`	No	The range to read (e.g., "Sheet1!A1:D10", "A1:D10"). Defaults to "A1:Z1000". Open-ended or oversized ranges are clamped to at most 1000 rows before the Sheets API request to bound memory use.	A1:Z1000
`include_notes`	No	If True, also fetch cell notes for the range. Defaults to False to avoid expensive includeGridData requests.
`spreadsheet_id`	Yes	The ID of the spreadsheet. Required.
`include_formulas`	No	If True, also fetch raw formula strings for cells that contain formulas. Useful for identifying cross-sheet references before writing back to a range. Defaults to False to avoid an extra API request.
`user_google_email`	Yes	The user's Google email address. Required.
`include_hyperlinks`	No	If True, also fetch hyperlink metadata for the range. Defaults to False to avoid expensive includeGridData requests.
`include_smart_chips`	No	If True, also fetch smart chips metadata (Drive files/folders and People chips) for the range. Defaults to False to avoid expensive includeGridData requests.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.28.0Sep 24, 2026

addedInput schema / properties / include_smart_chips

Added value: +{
+  "default": false,
+  "description": "If True, also fetch smart chips metadata (Drive files/folders\nand People chips) for the range. Defaults to False to avoid expensive includeGridData requests.",
+  "type": "boolean"
+}

Changed14 schema fields changedv1.0.1Jul 31, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / include_formulas

Added value: +{
+  "default": false,
+  "description": "If True, also fetch raw formula strings for cells that\ncontain formulas. Useful for identifying cross-sheet references before writing\nback to a range. Defaults to False to avoid an extra API request.",
+  "type": "boolean"
+}

addedInput schema / properties / include_hyperlinks

Added value: +{
+  "default": false,
+  "description": "If True, also fetch hyperlink metadata for the range.\nDefaults to False to avoid expensive includeGridData requests.",
+  "type": "boolean"
+}

addedInput schema / properties / include_notes

Added value: +{
+  "default": false,
+  "description": "If True, also fetch cell notes for the range.\nDefaults to False to avoid expensive includeGridData requests.",
+  "type": "boolean"
+}

addedInput schema / properties / range_name / description

Added value: +"The range to read (e.g., \"Sheet1!A1:D10\", \"A1:D10\").\nDefaults to \"A1:Z1000\". Open-ended or oversized ranges are clamped to\nat most 1000 rows before the Sheets API request to bound memory use."

removedInput schema / properties / range_name / title
```
Removed value: -"Range Name"
```

removedInput schema / properties / service

Removed value: -{
-  "title": "service",
-  "type": "string"
-}

addedInput schema / properties / spreadsheet_id / description
```
Added value: +"The ID of the spreadsheet. Required."
```
removedInput schema / properties / spreadsheet_id / title
```
Removed value: -"Spreadsheet Id"
```
addedInput schema / properties / user_google_email / description
```
Added value: +"The user's Google email address. Required."
```
removedInput schema / properties / user_google_email / title
```
Removed value: -"User Google Email"
```

changedInput schema / required

Previous value: -[
-  "service",
-  "user_google_email",
-  "spreadsheet_id"
-]New value: +[
+  "user_google_email",
+  "spreadsheet_id"
+]

removedInput schema / title

Removed value: -"read_sheet_valuesArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}

First observedv1.0.0Jun 10, 2025

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds the output shape (row number, tab-separated cells) which is genuinely useful context beyond annotations, but says nothing about the optional include_* flags or the 1000-row clamping behavior described in the schema.

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?

A single front-loaded sentence with zero waste; the output-format detail is the one non-obvious bit and it is included up front.

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?

Output schema exists and parameter coverage is complete, so the description needn't re-explain returns. However, given 7 parameters and a crowded spreadsheet sibling set, it could have clarified scope and routing without redundant detail.

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?

Schema description coverage is 100%, so all seven parameters including the include_notes/formulas/hyperlinks/smart_chips flags and the range default are fully documented in the schema. The description adds no parameter meaning, which is the baseline case when the schema does the heavy lifting.

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?

States a specific verb and resource: reads values from a specific range in a Google Sheet. Clear to an agent what it does, though it never distinguishes itself from nearby siblings such as get_spreadsheet_info or list_sheet_tables.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The agent must infer from the name alone that this is the read path versus modify_sheet_values for writes.

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

Deploy Server