Skip to main content
Glama
shakhin85

Google Sheets MCP Server

by shakhin85

append_rows

Append rows to the end of a specified sheet in Google Sheets by providing the spreadsheet ID, range, and values.

Instructions

Append rows to the end of a sheet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeYesThe A1 notation of the range to append to (e.g., 'Sheet1!A:D')
valuesYes2D array of rows to append
spreadsheet_idYesThe ID of the spreadsheet
Behavior2/5

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

The description does not disclose critical behavioral traits such as whether the tool handles extending the sheet automatically, what happens if the range doesn't match existing data size, or if it's destructive. No annotations are provided, so the description carries the full burden but falls short.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence), but it lacks important information that could be included without verbosity. It serves as a minimal statement rather than a well-structured description.

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?

Given the three parameters, no output schema, and no annotations, the description is insufficient. It does not explain the return value, error conditions, or how the append interacts with the sheet's existing data. Completeness is inadequate.

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 coverage is 100%, so the schema already describes all parameters. The description adds no extra meaning beyond the tool's purpose, so baseline 3 is appropriate.

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?

The description clearly states the action ('Append') and resource ('rows to the end of a sheet'). It effectively distinguishes from sibling tools like write_range (overwrite) and clear_range, though it could be more specific about the append behavior (e.g., automatically finds first empty row).

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?

No guidance is provided on when to use this tool versus alternatives like write_range or insert_dimension. There is no mention of prerequisites (e.g., sheet existence) or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shakhin85/google-sheets-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server