Skip to main content
Glama

workspace_append_sheet

Append rows to a Google Sheets table by specifying the spreadsheet ID, range, and values as a JSON 2D array.

Instructions

Append rows to a Google Sheets table (POST — adds rows after the last row in the table)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadsheetIdYesSpreadsheet ID (from URL: docs.google.com/spreadsheets/d/{id})
rangeYesA1 notation range to detect table (e.g. "Sheet1!A:C")
valuesYesRows to append as JSON string 2D array
valueInputOptionNoHow values are interpreted: USER_ENTERED parses dates/numbers, RAW stores as-isUSER_ENTERED
insertDataOptionNoINSERT_ROWS shifts existing data down; OVERWRITE replaces data below the tableINSERT_ROWS
Behavior4/5

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

The description adds value beyond annotations by specifying the HTTP POST method and exact behavior (appends after last row). Annotations already indicate non-idempotent and open world, and the description reinforces this without contradiction.

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, front-loaded sentence that conveys purpose and method without any unnecessary words.

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 core functionality. Although it does not mention return values or error handling, the annotations and schema compensate sufficiently.

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 description only adds overall context. It does not elaborate on individual parameters beyond what the schema provides, achieving the baseline for high coverage.

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 verb 'Append rows' and the resource 'Google Sheets table', and distinguishes from sibling tools like workspace_get_sheet and workspace_update_sheet by specifying appending after the last 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?

The description does not provide guidance on when to use this tool versus alternatives (e.g., workspace_update_sheet for overwriting rows). It only mentions the HTTP method, which is implicit.

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/fideguch/my_pm_tools'

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