Skip to main content
Glama

batch_update

Destructive

Execute multiple Google Sheets modifications in a single API call, including adding sheets, updating properties, and inserting or deleting rows and columns.

Instructions

Execute a batch update on a Google Spreadsheet using the full batchUpdate endpoint. This provides access to all batchUpdate operations including adding sheets, updating properties, inserting/deleting dimensions, formatting, and more.

Args: spreadsheet_id: The ID of the spreadsheet (found in the URL) requests: A list of request objects. Each request object can contain any valid batchUpdate operation. Common operations include: - addSheet: Add a new sheet - updateSheetProperties: Update sheet properties (title, grid properties, etc.) - insertDimension: Insert rows or columns - deleteDimension: Delete rows or columns - updateCells: Update cell values and formatting - updateBorders: Update cell borders - addConditionalFormatRule: Add conditional formatting - deleteConditionalFormatRule: Remove conditional formatting - updateDimensionProperties: Update row/column properties - and many more...

         Example requests:
         [
             {
                 "addSheet": {
                     "properties": {
                         "title": "New Sheet"
                     }
                 }
             },
             {
                 "updateSheetProperties": {
                     "properties": {
                         "sheetId": 0,
                         "title": "Renamed Sheet"
                     },
                     "fields": "title"
                 }
             },
             {
                 "insertDimension": {
                     "range": {
                         "sheetId": 0,
                         "dimension": "ROWS",
                         "startIndex": 1,
                         "endIndex": 3
                     }
                 }
             }
         ]

Returns: Result of the batch update operation, including replies for each request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadsheet_idYes
requestsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate destructiveHint=true. The description reinforces this by listing operations like insertDimension, deleteDimension, and updateCells, which imply mutability. However, it does not go beyond annotations to discuss side effects, error handling, or rate limits.

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?

The description is front-loaded with purpose but becomes lengthy with many examples and operation details. It is well-structured with clear sections (Args, Returns) but could be more concise by reducing verbosity in the operation list.

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

Completeness4/5

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

Given the tool's complexity and zero schema description coverage, the description is quite complete with examples and return type mentioned. However, it lacks mention of error scenarios, operation limits, or specifics about the output schema content.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description carries full burden. It explains spreadsheet_id as 'found in the URL' and thoroughly describes the requests parameter with examples of valid operations, adding significant meaning beyond the schema's empty descriptions.

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 it executes a batch update on a Google Spreadsheet using the full batchUpdate endpoint, providing access to all batchUpdate operations. This is a specific verb and resource, and it distinguishes from sibling tools like add_rows or update_cells by emphasizing the batch nature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the types of operations available (addSheet, insertDimension, etc.) and provides examples, but it does not explicitly guide when to use this tool versus siblings (e.g., batch_update_cells for cell updates only). It lacks direct exclusions or alternative suggestions.

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/socar-edwin/mcp-google-sheets-extended'

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