Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

sheets_batch_update

Send raw Sheets API batchUpdate requests to apply conditional formatting, filters, pivot tables, and other advanced spreadsheet changes in one call.

Instructions

Advanced: send raw Sheets API batchUpdate requests (conditional formatting, filters, pivot tables, etc.).

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

NameRequiredDescriptionDefault
requestsYes
spreadsheetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the description only needs to add context — but it does not. The examples chosen (formatting, filters, pivot tables) are all benign while 'etc.' silently covers batchUpdate request types that delete sheets, rows, or ranges, and the description never warns that raw requests can destroy data or that a malformed request may partially apply. This under-description is a meaningful risk for a raw mutation tool, though it does not directly assert anything contrary to the annotations.

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?

A single front-loaded sentence with the qualifier 'Advanced:' placed first, which is the right information ordering. The trailing 'etc.' is vague filler that could have been replaced with the destructive capability warning the tool actually needs.

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?

For a raw mutation endpoint with no output schema and zero schema coverage, the description should at minimum say what comes back (batchUpdate replies) and warn about destructive request types. It says neither, leaving the agent to guess at both response shape and risk profile.

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 carries the burden of explaining two undocumented parameters. 'Raw Sheets API batchUpdate requests' does usefully tell the agent that the requests array must follow Google's Request object format rather than an arbitrary shape, but nothing explains spreadsheetId or the required per-request structure beyond that pointer.

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 gives a specific verb and resource ('send raw Sheets API batchUpdate requests') and names concrete use cases (conditional formatting, filters, pivot tables), so the agent can tell this is the low-level escape hatch rather than a curated formatter like sheets_format. It stops short of naming which sibling it replaces when the request is simple, so it is clear but not fully differentiated.

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 leading 'Advanced:' signals this is not the default path and the examples imply it is for operations the structured tools cannot express, which is useful implied routing. However, there is no explicit 'use X instead for simple formatting/writes' statement and no stated preconditions, so the agent must infer the boundary itself.

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