Skip to main content
Glama
Sign In
MCP Google Sheets

MCP Google Sheets

by toantran201
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update Row

update_row

Overwrite cells in a single row from a given start column, updating only the specified columns without affecting the rest of the row.

Instructions

Overwrites cells in a single row, left to right, starting at start_column (default column A). Only the cells covered by values are written — cells outside that span are left untouched, so you can update specific columns without rewriting the whole row.

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>",
      "row_index": "<row_index>",
      "values": "<values>"
    },
    "name": "update_row"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes1D array of values written left-to-right starting at `start_column`
row_indexYes1-based row number in the sheet
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
start_columnNo1-based column to start writing at (e.g. 3 = column C). Default 1 (column A)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Without annotations, the description carries full burden. It discloses the partial overwrite behavior and the left-to-right writing, which is critical for understanding the tool's effect. However, it does not mention error handling or edge cases like out-of-range row indices.

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?

Two sentences efficiently convey the core behavior and key parameter details, with no wasted 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?

Given the moderate complexity (5 params, no output schema, no annotations), the description covers essential behavior for an agent to use the tool correctly. It lacks error handling or result description, but is largely sufficient.

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?

The schema already provides 100% coverage with descriptions for each parameter. The description adds context about start_column's default and the partial overwrite, but does not significantly expand beyond schema definitions.

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 it overwrites cells in a single row left-to-right starting at a specified column, distinguishing it from sibling tools like add_rows or delete_rows that add or remove rows.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance is provided, but the description implies it is for updating specific columns without rewriting the whole row. The sibling tool list offers context but no direct comparison.

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