Skip to main content
Glama

sheets append rows

sheets_append_rows

Append rows after the last row of an existing table in a Google Sheet, adding new data to a spreadsheet without overwriting existing content.

Instructions

Append rows after the last row of a table. Write operation.

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": {
      "spreadsheet_id": "<spreadsheet_id>",
      "range_a1": "<range_a1>",
      "values": "<values>"
    },
    "name": "sheets_append_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes
range_a1Yes
value_inputNoUSER_ENTERED
spreadsheet_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds that rows go after the last row of a table, but otherwise mostly restates that this is a write operation and does not explain side effects, failure behavior, or authentication requirements.

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 two short sentences and front-loads the key operation. The second sentence, 'Write operation,' is largely redundant with the annotations but does not create clutter.

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?

For a four-parameter mutation tool with no schema descriptions, the definition is too sparse. It gives the core purpose but omits parameter semantics, usage alternatives, and practical behavior, though the annotations and output schema cover some context.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It does not explain spreadsheet_id, range_a1, values structure, or value_input options, leaving all four parameters without semantic guidance.

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?

States a specific verb and resource: append rows after the last row of a table. It clearly distinguishes appending from overwriting, though it does not explicitly name a sibling such as sheets_update_range.

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?

Provides no guidance on when to choose this tool versus alternatives like sheets_update_range or sheets_clear_range. The only contextual hint is that it is a write operation.

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