Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

docs_batch_update

Send raw Google Docs API batchUpdate requests to apply styling, page breaks, headers, and other document changes in one operation.

Instructions

Advanced: send raw Google Docs API batchUpdate requests (for styling, page breaks, headers, 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": {
      "documentId": "<documentId>",
      "requests": "<requests>"
    },
    "name": "docs_batch_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestsYes
documentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, open-world mutation. The description adds real value by signalling that the payload is a raw API request list, so the agent knows the schema will not constrain or validate the request types. It does not warn that certain request kinds (e.g. deleting content ranges) can remove document content, nor what happens on a partially invalid batch.

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" first and parenthetical examples last. Efficient, though "etc." adds little and could be replaced by a pointer to the API reference.

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?

For an unconstrained escape-hatch tool with a free-form array payload and no output schema, an agent needs to know where the request format is defined and whether the batch is atomic. The description hints at the API but stops short of that guidance.

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 0%, so both documentId and requests are undocumented in the schema. The phrase "raw Google Docs API batchUpdate requests" is a useful pointer that requests must follow the external batchUpdate Request object shape, but documentId is never mentioned and no guidance is given on request ordering, atomicity, or size limits.

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?

States a specific verb and resource: it sends raw Google Docs API batchUpdate requests to a document. The word "Advanced" plus the examples (styling, page breaks, headers) distinguish it from the narrow siblings like docs_replace_text or docs_insert_table, which handle single operations.

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?

"Advanced" implies this is the escape hatch to use when simpler tools don't cover the operation, and the field examples give concrete triggers. However, no alternative is named explicitly and there is no statement of when NOT to use it (e.g. prefer docs_replace_text for simple text replacement).

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