Gmail Multi-Inbox MCP Server

sheets_append

Append rows to a Google Sheet after the last row with data. Provide account, spreadsheet ID, range, and a 2D array of values to add.

Instructions

Append rows to a Google Sheet after the last row with data.

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": {
      "account": "<account>",
      "spreadsheet_id": "<spreadsheet_id>",
      "range": "<range>",
      "values": "<values>"
    },
    "name": "sheets_append"
  }
}

Input Schema

Name	Required	Description
`range`	Yes	Sheet name or range to append to, e.g. "Sheet1".
`values`	Yes	2D array of rows to append.
`account`	Yes	Account id.
`spreadsheet_id`	Yes	Spreadsheet ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.2Aug 14, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It adds key behavioral context (appending after the last row with data), but does not disclose other important traits such as authorization needs, side effects, error handling, or behavior when the sheet is empty. It provides some value beyond the schema but is not comprehensive.

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 a single sentence that directly conveys the core functionality. It is front-loaded with the action and resource, contains no filler, and every word earns its place.

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 simple append operation, the description covers the essential behavior (append after last data row) while the schema fully documents all parameters. No output schema exists, but the tool's return value is likely minimal. It could be slightly more complete with notes on edge cases, but for its complexity it is adequately complete.

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%, so the baseline is 3. The description does not add new meaning to the parameters; it merely restates the concept of rows, which the schema already describes as a 2D array. It does not compensate further for any gaps because there are none.

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 the tool appends rows to a Google Sheet, specifically after the last row with data. It uses a specific verb 'append', identifies the resource 'Google Sheet', and distinguishes from siblings like sheets_write by emphasizing the append-after-last-row behavior.

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?

The description implies usage (adding rows at the end of a sheet) but does not explicitly mention when to use it over alternatives like sheets_write or sheets_update, nor does it state any exclusions or prerequisites. The guidance is inferred rather than explicit.

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

Deploy Server