Skip to main content
Glama
taylorwilsdon

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

by taylorwilsdon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Read Sheet Values

read_sheet_values
Read-onlyIdempotent

Fetch data from a Google Sheets range by spreadsheet ID and email. Optionally include formulas, notes, hyperlinks, or smart chips.

Instructions

Reads values from a specific range in a Google Sheet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
range_nameNoThe 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_notesNoIf True, also fetch cell notes for the range. Defaults to False to avoid expensive includeGridData requests.
spreadsheet_idYesThe ID of the spreadsheet. Required.
include_formulasNoIf 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_emailYesThe user's Google email address. Required.
include_hyperlinksNoIf True, also fetch hyperlink metadata for the range. Defaults to False to avoid expensive includeGridData requests.
include_smart_chipsNoIf 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

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.28.0
    • 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"
+}
  2. Changed14 schema fields changedv1.0.1
    • 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
+}
  3. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. However, the description itself adds no behavioral detail beyond the read-only intent; it does not mention range clamping to 1000 rows or the cost implications of include_* flags at the tool level. It is consistent with the annotations, so there is no contradiction.

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?

The description is a single clear sentence with no filler and the purpose is front-loaded. However, it is so minimal that it contributes little beyond the title and does not use available space to provide selection context.

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?

Given the rich schema, output schema, and annotations, the description is sufficient for invocation once the tool is selected. But with many sibling tools, the description alone does not fully support correct tool selection; it lacks guidance on when to read values versus inspecting spreadsheet metadata or modifying values.

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 description coverage is 100%, with detailed documentation for all seven parameters, including defaults, required fields, clamping behavior, and cost warnings. The tool description adds no new semantic information about parameters beyond the vague notion of a "specific range," so the baseline 3 applies.

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 identifies a read operation (verb "reads") targeting cell values in a specific range of a Google Sheet. This differentiates it from sibling write tools like modify_sheet_values and metadata tools like get_spreadsheet_info. It is specific enough to be actionable and not a mere tautology.

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?

There is no explicit when-to-use, when-not, or alternative-tool guidance. The description only states what the tool does, leaving an agent to infer when to choose it over related tools such as get_spreadsheet_info or modify_sheet_values.

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

Deploy Server

Other Tools