Skip to main content
Glama
EveryInc

google-workspace-mcp-server

by EveryInc

Batch Update Spreadsheet

sheets_batch_update
Destructive

Apply batch updates to Google Spreadsheets, including formatting, charts, filters, and conditional formatting rules, using a single API request.

Instructions

Apply batch updates to a Google Spreadsheet (formatting, charts, filters, conditional formatting, etc.).

Args:

  • spreadsheet_id (string): The ID of the Google Spreadsheet to update

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

Common request types:

  • updateCells: Update cell data and formatting

  • addSheet: Add a new sheet

  • deleteSheet: Delete a sheet

  • updateSheetProperties: Rename sheet, change grid size

  • mergeCells: Merge cell ranges

  • addConditionalFormatRule: Add conditional formatting

  • addChart: Add a chart

  • setDataValidation: Add data validation rules

  • addFilterView: Add filter views

  • repeatCell: Apply formatting to a range

See Google Sheets API batchUpdate documentation for full request schema.

Returns: { "spreadsheetId": string, "replies": array }

Examples:

  • Add sheet: requests=[{ "addSheet": { "properties": { "title": "NewSheet" } } }]

  • Bold range: requests=[{ "repeatCell": { "range": {...}, "cell": { "userEnteredFormat": { "textFormat": { "bold": true } } }, "fields": "userEnteredFormat.textFormat.bold" } }]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spreadsheet_idYesThe ID of the Google Spreadsheet to update
requestsYesArray of batch update request objects (see Google Sheets API batchUpdate documentation)
Behavior4/5

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

Annotations already show destructiveHint=true. The description adds context by listing destructive operations (deleteSheet) and provides examples of many request types, enhancing understanding of side effects.

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?

Well-organized with Args, Common request types, Returns, Examples. Each section is useful. Somewhat lengthy but justified given complexity. Front-loaded with main purpose.

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 complexity and lack of output schema, the description covers common request types, provides examples, and describes return value. Sufficient for an agent to understand capabilities.

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?

Schema coverage is 100%, but the description adds crucial meaning beyond schema by listing common request types, providing examples, and explaining the structure of the requests array. This is essential for correct usage.

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?

Clearly states 'Apply batch updates to a Google Spreadsheet' with specific verb and resource, and lists common request types like addChart, deleteSheet, etc. Distinguishes from sibling tools by being a batch update.

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?

No explicit when-to-use or when-not-to-use compared to alternatives like sheets_update_values or sheets_append_values. The description implies it for complex updates but lacks direct guidance.

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