Skip to main content
Glama
salviz

Google Workspace MCP Server

by salviz

sheets_append

Append new rows of data to a specified Google Spreadsheet range using a 2D array input.

Instructions

Append rows to a Google Spreadsheet

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeYesCell range in A1 notation, e.g. 'Sheet1!A1:D10'
valuesYesJSON string of a 2D array, e.g. [["A1","B1"],["A2","B2"]]
spreadsheetIdYesThe spreadsheet ID
Behavior2/5

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

No annotations provided, and description is minimal. Does not disclose behavioral traits like if rows are added at the end, how existing data is affected, or required permissions. The word 'append' implies addition but lacks detail.

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?

One sentence is concise but too brief for a tool with three required parameters. Lacks necessary context for effective use.

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?

No output schema, and description does not explain return values, error conditions, or behavior on success. For a tool that modifies a spreadsheet, more context is needed for safe invocation.

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 baseline is 3. Description adds no parameter-specific information beyond what the schema provides, which already explains range, values, and spreadsheetId.

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?

Description uses specific verb 'append' and resource 'rows to a Google Spreadsheet', clearly distinguishing it from sibling tools like sheets_read (read), sheets_write (overwrite), sheets_create (create new sheet), and sheets_clear (clear data).

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 on when to use this tool versus alternatives. Does not mention when appending is appropriate, such as adding rows to an existing sheet versus replacing data with sheets_write.

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/salviz/google-mcp-server'

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