Skip to main content
Glama

read_sheet_values

Read cell values from a Google Sheets A1 range, optionally including formulas, notes, or hyperlinks. Output limited to 50 rows; widen range or paginate for more.

Instructions

Read cell values from an A1 range (optionally with formulas/notes).

Output is capped at 50 rows for readability — widen the range or paginate manually for more. For writing use modify_sheet_values. For appending to a table use append_table_rows. Requires the spreadsheets.readonly OAuth scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
spreadsheet_idYesSpreadsheet ID from list_spreadsheets.
range_nameNoA1 notation, e.g. "Sheet1!A1:D10", "A:D", or unqualified "A1:D10" (first sheet). Default "A1:Z1000".A1:Z1000
include_hyperlinksNoTrue adds a hyperlink-metadata section for cells containing URLs. Triggers an includeGridData request — more expensive.
include_notesNoTrue adds a cell-notes section. Same cost caveat as include_hyperlinks.
include_formulasNoTrue fetches raw formula strings (=SUM(...), etc.) alongside displayed values — useful before writing back to avoid clobbering cross-sheet references.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses output cap (50 rows) and OAuth scope requirement. No annotations provided, so description carries full burden. Cost info for hyperlinks/notes is in parameter descriptions but not main body.

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?

Four sentences, front-loaded with core purpose, each sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, limitations, alternatives, and authorization fully. Output schema handles return format, so description is complete.

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 coverage is 100%, but description adds practical guidance on range parameter use due to output cap, providing semantics beyond schema.

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?

Clearly states 'Read cell values from an A1 range' with optional formulas/notes. Distinguishes from sibling tools modify_sheet_values and append_table_rows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool vs write/modify alternatives, and mentions output cap behavior and required OAuth scope.

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/HuntsDesk/ve-gws'

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