Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

sheets_append_rows

Append rows to the end of a Google Sheets tab to add new records without overwriting existing data.

Instructions

Append rows after the last row of data in a tab.

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>",
      "rows": "<rows>"
    },
    "name": "sheets_append_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoSheet1
rowsYes
spreadsheetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description usefully adds that insertion happens after existing data rather than overwriting it, but stays silent on behavior the annotations do not cover, such as whether a missing tab is created (the schema defaults tab to 'Sheet1') or what is returned after the append.

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?

A single front-loaded sentence with no redundant or throat-clearing wording. It is efficient, though its terseness is part of why parameter and behavioral detail is absent.

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 mutation tool with three parameters at 0% schema coverage and no output schema, the one-line description leaves too much unknown. An agent cannot tell from it what shape rows must take, whether the default tab will be created, or what a successful append yields.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden and largely drops it. It names 'rows' and alludes to 'tab' but never explains the required spreadsheetId, the 'Sheet1' default, or that rows is an array of arrays of scalars.

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 ('append') plus resource ('rows') and placement semantics ('after the last row of data in a tab'), which distinguishes it from an overwriting tool like sheets_write. It stops short of naming a sibling explicitly, so it is clear but not fully differentiated.

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?

Use case is only implied: 'after the last row of data' hints that this is for adding data without overwriting existing content. There is no explicit when-to-use/when-not statement, no mention of what to do instead when you want to replace a range, and no prerequisites such as required permissions or whether the target tab must already exist.

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