gg-mcp

Overview Schema Source Related Servers Discussions Admin

batch_update_spreadsheet

Update multiple ranges in a Google Spreadsheet in a single batch request. Specify the range and values as a JSON array.

Instructions

Batch update multiple ranges. Data format: JSON array of {range, values}, e.g. '[{"range":"Sheet1!A1","values":[["X"]]}]'.

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_id": "<spreadsheet_id>",
      "data": "<data>"
    },
    "name": "batch_update_spreadsheet"
  }
}

Input Schema

Name	Required	Description	Default
`spreadsheet_id`	Yes
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Jun 23, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It only covers data format and an example, omitting whether updates are destructive, atomic, or have limits.

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?

Extremely concise: one sentence plus a practical example. Every part adds value with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a two-parameter tool, but lacks behavioral details (error handling, atomicity) and does not mention that it is a batch version of update_spreadsheet.

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 0%, so the description adds meaning for the data parameter with format and example, but spreadsheet_id is left undescribed.

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 'Batch update multiple ranges' with a specific verb and resource, distinguishing it from sibling tools like update_spreadsheet which likely handles single-range updates.

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?

The description implies usage when updating multiple spreadsheet ranges, but lacks explicit when-to-use or when-not-to-use guidance, and no alternatives are mentioned.

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