Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

sheets_values_append

Append new rows of values after the last row of a Google Sheets range. Use it to add data to existing spreadsheets without overwriting current cells.

Instructions

Append values after the last row of a spreadsheet range.

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>",
      "range": "<range>",
      "valueInputOption": "<valueInputOption>",
      "values": "<values>"
    },
    "name": "sheets_values_append"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeYesA1 notation range to append to
valuesYes2D array of values as JSON string
spreadsheetIdYesThe spreadsheet ID
valueInputOptionYesRAW or USER_ENTERED

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

While the annotations mark it as a write operation (not read-only), the description adds the crucial behavioral context that it appends specifically 'after the last row.' This defines how the tool behaves relative to the existing dataset size.

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 definition is a single, clear, and highly focused sentence with no extraneous wording, maximizing clarity and minimizing cognitive load for the agent.

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 data manipulation tool, the description successfully conveys the core functional behavior (appending to the end of a range). Given the rich schema and available annotations, it provides all necessary behavioral constraints for correct 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?

With 100% schema description coverage provided in the input schema, the description primarily confirms the actions the parameters enable without needing to add semantic depth beyond what the schema already details. A baseline score is appropriate.

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 uses the specific action 'append values' and clearly defines the target 'spread-sheet range', distinguishing it from 'get' or 'update' siblings by specifying the nature of the modification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly dictates the context of use: adding data 'after the last row.' This implies the tool is used when new records are being added sequentially rather than replacing existing content.

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