Skip to main content
Glama
Sign In
google-sheets-mcp

google-sheets-mcp

by AurelioCecchi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Append rows

append_rows

Add rows after the last occupied row of a table to insert new data without altering existing entries.

Instructions

Adds rows after the last occupied row of the given table. This is the safe way to insert new data without touching what is already there.

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": {
      "spreadsheetId": "<spreadsheetId>",
      "range": "<range>",
      "values": "<values>"
    },
    "name": "append_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYesTab or range identifying the table, e.g. 'Sheet1' or 'Sheet1!A:D'.
valuesYesRows to append.
spreadsheetIdYesSpreadsheet ID, or its full URL. The ID is the segment between /d/ and /edit in the URL.
valueInputOptionNoUSER_ENTERED parses values as if typed by hand (formulas, dates, numbers). RAW stores them literally as strings.USER_ENTERED

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the most important behavioral trait for an append tool: rows land after the last occupied row and existing data is preserved. However, it says nothing about permissions/auth, return payload, partial-append failure behavior, or how trailing blank rows are treated.

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 sentences, front-loaded with the operation and followed by the differentiator. Nothing redundant and no wasted framing.

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?

For a 4-parameter, 100%-documented schema with no output schema and no annotations, the description covers the core append semantics adequately. Minor gaps remain around return value expectations and failure/partial-write behavior, but nothing critical to invoking it correctly is missing.

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% and the schema already documents range, values, spreadsheetId, and the RAW/USER_ENTERED enum. The description's only nod to parameters is the loose phrase 'the given table', adding no format or encoding detail beyond the schema, so the baseline 3 applies.

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?

Specific verb+resource ('Adds rows') with a precise placement rule ('after the last occupied row of the given table'). It implicitly separates itself from overwriting siblings like write_range or update_row via 'without touching what is already there', but never names a sibling explicitly.

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

Usage Guidelines4/5

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

'This is the safe way to insert new data without touching what is already there' gives a clear selection criterion: use it when you want additive inserts rather than replacement. It stops short of naming an alternative (e.g. write_range) or stating when-not to use it, so it is clear context without explicit routing.

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

Deploy Server

Other Tools