mcp-google-sheets

append_rows

Destructive

Append rows of data after the last row with content in a Google Sheet. Add log entries or new records without needing the exact row number.

Instructions

Append rows of data after the last row with content in a sheet. Useful for adding log entries or new records without knowing the exact row number.

Args: spreadsheet_id: The ID of the spreadsheet sheet: Sheet/tab name values: List of rows, each row is a list of cell values. Example: [["Alice", 30, "Seoul"], ["Bob", 25, "Busan"]]

Returns: The range where data was appended and number of rows added

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>",
      "sheet": "<sheet>",
      "values": "<values>"
    },
    "name": "append_rows"
  }
}

Input Schema

Name	Required	Description	Default
`spreadsheet_id`	Yes
`sheet`	Yes
`values`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.2Jun 21, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description explains the behavior of appending after the last row with content, adding value beyond the destructiveHint annotation. It does not contradict annotations, but could mention potential side effects like overwriting if there is no blank row.

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 concise with a clear structure: purpose, usage, parameters, and returns. The example is helpful but adds some length; however, it is justified.

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?

The description covers purpose, parameter details, and return value. For a straightforward append operation, this is complete. The tool has no complex behaviors or edge cases that would require more.

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?

Despite 0% schema coverage, the description defines all three parameters and provides a concrete example for 'values.' This compensates for the missing schema descriptions and adds significant meaning.

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 it appends rows after the last row with content, distinguishing it from tools like update_cells (specific range) and add_rows (add empty rows). The verb 'append' and resource 'rows' are specific, and the usage example solidifies the purpose.

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?

The description explicitly says 'Useful for adding log entries or new records without knowing the exact row number,' which guides when to use. It does not explicitly mention alternatives or when not to use, but the context is clear enough for most agents.

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