Skip to main content
Glama

sheets_update_values

Update cell values in specified ranges of Google Sheets. Use fixed or flexible A1 notation ranges, providing a 2D array of values that automatically expands to fit data.

Instructions

Update values in a specified range of a Google Sheets spreadsheet. Examples:

  • Fixed range "A1:C3" - must provide exactly 3 rows

  • Flexible range "A1" - will expand to fit all provided rows

  • To update rows 42-74 (33 rows), use "A42" not "A42:E53" IMPORTANT: Empty rows in your data array still count as rows!

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeYesThe A1 notation range to update. Use "Sheet1!A1:B10" for exact range (must match row count exactly) or "Sheet1!A1" for flexible range that auto-expands based on data. TIP: If updating multiple rows with varying content, use flexible range (e.g., "A42" instead of "A42:E53") to avoid row count mismatch errors.
valuesYesA 2D array of values to update, where each inner array represents a row
spreadsheetIdYesThe ID of the spreadsheet (found in the URL after /d/)
valueInputOptionNoHow the input data should be interpreted (default: USER_ENTERED)
Behavior4/5

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

With no annotations provided, the description carries the full burden. It explains behavioral traits: fixed range requires exact row count, flexible range auto-expands, and empty rows are counted. It could mention that the operation overwrites existing data and potential authorization needs, but overall it is fairly transparent.

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?

The description is concise and well-structured, front-loading the main action and using bullet-like examples. Every sentence adds value without redundancy, making it easy for an AI agent to parse quickly.

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?

Given 4 parameters (3 required, 1 enum) and no output schema, the description is fairly complete. It explains range behavior and a critical caveat about empty rows. It lacks details on return values or error handling, but the absence of output schema lessens the need; overall adequate.

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 significant value beyond the schema by providing examples and tips for the range parameter (e.g., using 'A42' instead of 'A42:E53') and clarifying the empty row behavior, enhancing usability.

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 states the tool updates values in a specified range of a Google Sheets spreadsheet, using a specific verb and resource. It distinguishes from siblings like `sheets_append_values` or `sheets_clear_values` by focusing on overwriting existing data within a range.

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

Usage Guidelines4/5

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

The description provides practical examples and an important note about empty rows, offering implicit guidance on when to use fixed vs flexible ranges. However, it does not explicitly contrast with alternatives like append or clear, leaving some usage context unaddressed.

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/freema/mcp-gsheets'

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