Skip to main content
Glama
Sign In
MCP Google Sheets

MCP Google Sheets

by toantran201
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Add Rows

add_rows

Append multiple rows of data to the bottom of a Google Sheets tab. Provide spreadsheet URL, sheet tab name, and a 2D array of values.

Instructions

Appends rows to the bottom of a sheet 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": {
      "spreadsheet": "<spreadsheet>",
      "sheet_name": "<sheet_name>",
      "values": "<values>"
    },
    "name": "add_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes2D array of rows to append
sheet_nameYesTarget sheet tab name
spreadsheetYesTarget spreadsheet: a full Google Sheets URL (https://docs.google.com/spreadsheets/d/<ID>/edit...) or a bare spreadsheet ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations present, so description must fully cover behavior. Only states 'appends rows to bottom' without disclosing if existing data is affected, permission requirements, error handling, or maximum row limits (though schema has some limits).

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?

Single sentence is very concise and front-loaded, but could include more detail without becoming verbose. No wasted words.

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?

Tool is simple but the description lacks usage context, behavioral details, and guidance for a user who might confuse it with update_row or find_rows. With no output schema or annotations, more description is warranted.

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 baseline is 3. The description adds no additional meaning beyond the parameter names and descriptions already in the schema.

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 'Appends rows to the bottom of a sheet tab' clearly specifies the verb (appends), the resource (rows), and the location (bottom of sheet tab), distinguishing it from siblings like add_columns or update_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 on when to use this tool versus alternatives such as find_rows with update, or insert vs append. No exclusions or prerequisites provided.

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

Deploy Server

Other Tools