Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

slides_batch_update

Send raw Google Slides API batchUpdate requests to update shapes, tables, and styling in a presentation.

Instructions

Advanced: send raw Google Slides API batchUpdate requests (shapes, tables, styling, 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": {
      "presentationId": "<presentationId>",
      "requests": "<requests>"
    },
    "name": "slides_batch_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestsYes
presentationIdYes

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 readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the mutation profile is known. The description adds real value by disclosing that this is a raw passthrough to the Slides API, meaning arbitrary unvalidated request objects, but it omits whether changes are reversible, what permissions/scope are required, or how failures mid-batch are handled.

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 ordering for a routing hint. The trailing 'etc.' is mildly vague but costs little given the short length.

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 a high-flexibility tool that takes an arbitrary, untyped request array, the definition is thin: it does not say which batchUpdate request types are supported, whether the server validates payloads, or what a partial failure looks like. Annotations cover the mutation flags and there is no output schema to explain, so the gap is moderate rather than severe.

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 must carry the parameter burden. It does clarify that 'requests' holds Google Slides API batchUpdate request objects (shapes, tables, styling), pointing the agent at the upstream API contract, but it says nothing about presentationId or the request-object shape, which the schema leaves as arbitrary properties.

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 states a specific verb and resource: sending raw Google Slides API batchUpdate requests, with examples of what the payload can contain (shapes, tables, styling). The word 'raw' implicitly separates it from the targeted siblings like slides_add_text_box or slides_set_text, though it never names an alternative explicitly.

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 'Advanced:' prefix signals this is a power-user escape hatch rather than the default path, which is useful implied guidance. However, there is no explicit when-to-use/when-not statement naming a specific alternative (e.g., 'prefer slides_set_text for plain text edits'), so an agent must infer the routing decision.

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