ai-toolkit

update_sheet_range

Overwrite a defined range in a Google Sheet with new values, leaving row positions unchanged. Use to set data at exact coordinates or edit existing cells in place.

Instructions

Write values into an explicit range, overwriting whatever is there.

Use this for deterministic placement (no auto-detection): to put a new row exactly at row n, read the sheet first, then pass range="Sheet1!A<n>". Also used to edit an existing row in place (e.g. change a status cell). It overwrites the target cells but does not shift other rows — use insert_sheet_rows when you need to add a row between existing ones.

sheet_id is the spreadsheet's ID (from its URL) and is required. range is A1 notation anchoring the top-left of the write, e.g. Sheet1!A11 (the block grows to fit values) or an explicit Sheet1!A11:E11. values is a list of rows, each a list of cell strings — pass [["a", "b", "c"]] for a single row. Read the header row first so columns line up. value_input_option USER_ENTERED parses dates/numbers/formulas like typing; RAW stores text verbatim. Returns the range that was written.

Input Schema

TableJSON Schema

Name	Required	Default
`range`	Yes
`values`	Yes
`sheet_id`	Yes
`value_input_option`	No	USER_ENTERED

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 24, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations, the description carries the full responsibility and does so well: it discloses overwriting behavior, non-shifting of other rows, value_input_option parsing semantics (USER_ENTERED vs RAW), and the return value. No required behavioral trait is hidden.

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 organized into purpose, usage scenarios, and parameter details. Every sentence adds value, and the most decision-relevant information (overwrite, no shifting, alternative tool) is front-loaded. It is detailed yet free of padding.

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?

For a 4-parameter tool with zero schema coverage and no annotations, the description covers purpose, when to use it, parameter semantics, examples, return value, and caveats about reading first. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates. It explains sheet_id, range with A1 notation examples, values as a list of rows with a concrete example, and value_input_option with distinct USER_ENTERED and RAW semantics. This adds meaning far beyond the bare schema properties.

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?

States a specific verb and resource: 'Write values into an explicit range, overwriting whatever is there.' This clearly distinguishes the tool from siblings like insert_sheet_rows and append_sheet_row by emphasizing deterministic placement rather than auto-detection or shifting.

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?

Provides explicit usage context: use for deterministic placement at a known row, edit existing rows, and avoid when inserting rows between existing ones — 'use insert_sheet_rows when you need to add a row between existing ones.' Also instructs to read the sheet and header first, giving actionable guidance.

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