Skip to main content
Glama

Coline

Change sheet rows

update_sheet_rows
Destructive

Adds, updates or deletes rows in a sheet table. Adds and updates take cell values keyed by column name; updates and deletes take row ids from read_sheet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>",
      "sheetId": "<sheetId>"
    },
    "name": "update_sheet_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
addRowsNo
sheetIdYesSheet id from search, fetch or create_sheet.
tableIdNoA table in the sheet; default: the one it opens on.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
updateRowsNo
deleteRowIdsNo

Output Schema

NameRequiredDescriptionDefault
urlYes
sheetIdYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is carried by structured data. The description adds real context by disclosing where row ids must come from (read_sheet), but says nothing about whether deletions are irreversible, how partial failures in a mixed batch are handled, or the 500-item cap behavior. Useful addition over annotations, but thin for a destructive multi-mode mutation.

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?

Two short sentences, zero filler. The first establishes the three operations; the second front-loads the input requirements that differ per mode. Nothing is repeated from the title or annotations.

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

Completeness3/5

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

An output schema exists and annotations cover the destructive/idempotency profile, so the description need not explain returns or safety. However, for a 6-parameter tool with three distinct mutation modes, it omits whether modes can be combined in one call, ordering/atomicity semantics, and any result reporting for partially applied batches — meaningful gaps an agent would want before invoking a destructive call.

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?

With only 50% schema description coverage, the description does compensating work: it maps addRows/updateRows to 'cell values keyed by column name' and updateRows/deleteRowIds to 'row ids from read_sheet', which is meaning the schema alone does not convey about how rows are addressed. It leaves tableId's defaulting and the workspace/sheetId sourcing entirely to the schema, so not fully complete, but clearly value-adding.

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 names three specific operations (add, update, delete) against a concrete resource (rows in a sheet table), so the agent knows this is the row-mutation tool rather than a read tool like read_sheet or list_sheet_rows. It stops short of explicitly naming the read siblings as the non-mutating alternatives, but the verb+resource pairing is unambiguous.

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

Usage Guidelines3/5

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

It gives per-mode input guidance — adds/updates need cell values keyed by column name, updates/deletes need row ids sourced from read_sheet — which implies a read-then-mutate workflow. It never states when to prefer this tool over read_sheet/list_sheet_rows, whether the three modes can be mixed in one call, or any prerequisite permissions, so the guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources