Skip to main content
Glama
EveryInc

google-workspace-mcp-server

by EveryInc

Batch Update Google Document

docs_batch_update
Destructive

Apply batch updates to a Google Doc to insert, update, or delete text, formatting, images, and tables using the Google Docs API.

Instructions

Apply batch updates to a Google Doc (insert/update/delete text, formatting, images, tables).

Args:

  • document_id (string): The ID of the Google Doc to update

  • requests (array): Array of batch update request objects

Common request types:

  • insertText: { insertText: { location: { index: 1 }, text: "Hello" } }

  • deleteContentRange: { deleteContentRange: { range: { startIndex: 1, endIndex: 10 } } }

  • updateTextStyle: { updateTextStyle: { range: {...}, textStyle: {...}, fields: "bold" } }

  • insertInlineImage: { insertInlineImage: { location: {...}, uri: "https://..." } }

  • insertTable: { insertTable: { rows: 3, columns: 3, location: {...} } }

See Google Docs API batchUpdate documentation for full request schema.

Returns: { "documentId": string, "replies": array, "writeControl": object }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
document_idYesThe ID of the Google Doc to update
requestsYesArray of batch update request objects (see Google Docs API batchUpdate documentation)
Behavior3/5

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

Annotations already declare destructiveHint=true. Description lists common request types but does not add behavioral details beyond annotations (e.g., error handling, rate limits, permanence of changes). No contradiction found.

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?

Description is moderately concise with clear sections (Args, Common request types, Returns). Examples are helpful but add length; still well-structured.

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

Completeness5/5

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

Despite no output schema, description details the return structure. Covers input parameters with examples and output format, making it self-contained for a batch update tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema provides 100% coverage with basic descriptions. Description adds significant value by providing concrete examples of common request types (insertText, deleteContentRange, etc.), aiding understanding of the 'requests' parameter beyond the schema.

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?

Title 'Batch Update Google Document' and description 'Apply batch updates to a Google Doc (insert/update/delete text, formatting, images, tables)' provide a specific verb+resource. Distinguishes well from sibling tools like docs_create_document and docs_get_document.

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?

Description implies use for batch updates but does not explicitly state when to use this tool over alternatives like sheets_batch_update or docs_create_document. No exclusion criteria or context on prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EveryInc/google-workspace-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server