Skip to main content
Glama

sheets_batch_update_values

Update multiple ranges in a Google Sheet at once by providing range-value pairs and a spreadsheet ID.

Instructions

Update values in multiple ranges of a Google Sheets spreadsheet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesArray of range-value pairs to update
spreadsheetIdYesThe ID of the spreadsheet (found in the URL after /d/)
valueInputOptionNoHow the input data should be interpreted (default: USER_ENTERED)
Behavior2/5

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

The description does not disclose behavioral traits such as whether it overwrites existing cells, authorization requirements, rate limits, or response behavior. With no annotations provided, the description carries full burden but fails to convey these important details.

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 concise sentence that efficiently communicates the tool's core function. It is front-loaded and waste-free, though it could potentially be slightly expanded with key behavioral information without losing conciseness.

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

Completeness2/5

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

The description lacks completeness for a batch operation tool. It does not mention return values, error handling, limits, or the fact that it updates in a single API call. With no output schema, the agent lacks essential context for correct usage.

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%, so the input schema already documents all parameters thoroughly. The description adds no additional semantic meaning beyond what the schema provides, meeting the baseline for this dimension.

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?

The description clearly states it updates values in multiple ranges of a Google Sheets spreadsheet. It specifies the verb 'update' and the resource 'values in multiple ranges', distinguishing it from single-range updates like sheets_update_values, though not explicitly mentioning that differentiation.

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 is provided on when to use this tool versus alternatives like sheets_update_values or sheets_append_values. It does not mention prerequisites, context, or scenarios where batch update is appropriate.

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