Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

slides_set_text

Replaces all text in a Google Slides shape or text box using its objectId from slides_read. Pass a string for plain text or an array for bullet points.

Instructions

Replace all text inside one shape/text box (objectId from slides_read).

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>",
      "objectId": "<objectId>",
      "text": "<text>"
    },
    "name": "slides_set_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesArray = bullets
objectIdYes
presentationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write nature is known. The description adds real context beyond that by stating the replacement is total ("all text inside") rather than partial, but says nothing about consequences, return values, or whether text runs/styling are preserved.

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 a parenthetical hint and no wasted words. Density is good, though the parenthetical mixes prerequisite guidance into a purpose statement.

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?

With no output schema and only three required parameters, the description covers enough for correct invocation: target, identifier source, and total-replacement semantics. It is thin on what a successful call returns or mutates in adjacent content.

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 33%, so the description has to compensate somewhat. It usefully clarifies that objectId comes from slides_read, but presentationId and the shape of the text payload are only partly addressed, and the "Array = bullets" semantics live in the schema rather than the description.

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?

Specific verb and resource: "Replace all text inside one shape/text box", naming the exact target unit. It stops short of distinguishing itself from the sibling slides_replace_text, so an agent must guess which of the two replace operations to pick.

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?

Implies the intended flow by directing the agent to source objectId from slides_read, which is genuine prerequisite guidance. It gives no when-not guidance or contrast with slides_replace_text, leaving usage inferred.

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