mcp-google-sheets-server

sheets_batch_update

Execute multiple spreadsheet update operations in a single request to reduce API calls and improve performance.

Instructions

Perform multiple operations in a single request for better performance

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>",
      "requests": "<requests>"
    },
    "name": "sheets_batch_update"
  }
}

Input Schema

Name	Required	Description	Default
`requests`	Yes	Array of update requests to perform
`spreadsheetId`	Yes	The ID of the spreadsheet

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Sep 7, 2026

TDQS

C2.7/5.0

Behavior1/5

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

The description provides no behavioral details such as whether the batch is atomic, how partial failures are handled, or any authentication/permission requirements. With no annotations, this lack of transparency leaves the agent without critical information about side effects or error handling.

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, clear sentence that leads with the core action. It contains no extraneous words and is appropriately concise for the tool's purpose.

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?

The description omits essential context such as the permissible request types, the response format, or any constraints like maximum batch size. While the sibling tools and name imply a Sheets batch operation, the description alone is not complete enough for an agent to invoke it correctly without additional assumptions.

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 covers both parameters with basic descriptions, and the tool description adds no further meaning. The 'requests' parameter is still vague—its element structure is unexplained—but the baseline for high schema coverage is 3, and no additional insight is provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the primary action—performing multiple operations in a single request—which is distinct from single-operation tools. However, it does not specify which operations are included, leaving some ambiguity about the tool's scope.

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 only guidance is 'for better performance,' which implies batching but does not explicitly state when to use this instead of individual update tools. No comparison to alternatives like sheets_update_data or sheets_clear_range is provided, so an agent cannot easily decide when this is the appropriate choice.

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