Skip to main content
Glama
taylorwilsdon

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

by taylorwilsdon
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

Read Sheet Values

read_sheet_values
Read-onlyIdempotent

Read values, formulas, notes, and hyperlinks from a specified range in a Google Sheet, enabling access to spreadsheet data for further processing.

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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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
+}
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral details beyond the obvious 'reads values'; it doesn't mention range clamping, default behaviors, or return format. It provides minimal additional value beyond annotations.

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 sentence with zero waste. It clearly states the core purpose and relies on the schema for details, making it an appropriately sized description.

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?

The tool is simple, annotations cover safety, schema covers all parameters, and an output schema exists. However, the description lacks usage context such as when to choose this over other sheet tools, and doesn't mention the required user_google_email or that it's a read-only operation. It's adequate but leaves room for improvement in guiding selection.

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 coverage is 100%, with detailed parameter descriptions including defaults, clamping behavior, and performance implications (e.g., includeGridData). The description itself adds no parameter semantics, but the baseline of 3 is appropriate given the schema carries the full burden.

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?

Description uses a specific verb ('reads') and resource ('values from a specific range in a Google Sheet'), clearly indicating the tool's function. It doesn't explicitly differentiate from siblings like get_spreadsheet_info or list_spreadsheets, but the action is 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?

No guidance on when to use this tool versus alternatives such as modify_sheet_values, format_sheet_range, or get_spreadsheet_info. The description only states what it does, leaving the agent to infer usage context without explicit exclusions or alternative recommendations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/taylorwilsdon/google_workspace_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server