Skip to main content
Glama

modify_sheet_values

Write, overwrite, or clear values in a specified A1 range in Google Sheets. Supports USER_ENTERED or RAW input options.

Instructions

Write, overwrite, or clear values in an A1 range.

Side effects: overwrites existing cells in the exact range. To append new rows to a table use append_table_rows instead. For formatting use format_sheet_range. Requires the spreadsheets OAuth scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
spreadsheet_idYesSpreadsheet ID.
range_nameYesA1 range, e.g. "Sheet1!A1:D10". Range extent determines how many cells are overwritten regardless of values length — for example a 10x4 range clears leftover cells not covered by values.
valuesNo2D array of row arrays (e.g. [["a", "b"], ["c", "d"]]), or a JSON string. Required unless clear_values=True.
value_input_optionNo"USER_ENTERED" (default — strings parsed as dates/numbers/formulas, matches typing into the UI) or "RAW" (strings stored verbatim; formulas stored as literal text).USER_ENTERED
clear_valuesNoTrue clears the range instead of writing. Ignores `values`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses side effects (overwriting existing cells) and explains that the range extent determines overwrite area and clears leftover cells. It could mention atomicity or limits, but provides sufficient transparency.

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 three sentences with no waste. The first sentence states purpose, the second covers side effects and alternatives, and the third notes OAuth scope. It is front-loaded and efficient.

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 the complexity (6 params, 3 required) and the presence of an output schema, the description covers purpose, side effects, alternatives, and scope. It does not need to explain return values. It is complete enough for correct selection and use.

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 description coverage is 100%, so the baseline is 3. The description adds no extra detail beyond the schema for parameters, but the schema already documents each parameter adequately.

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 writes, overwrites, or clears values in an A1 range, with a specific verb and resource. It distinguishes itself from siblings by naming append_table_rows and format_sheet_range as alternatives.

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?

The description explicitly tells when not to use this tool (append rows, formatting) and points to specific alternatives. It also mentions the required OAuth scope, providing clear usage context.

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