Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

slides_replace_text

Replaces text across all slides or selected slides in a Google Slides presentation, letting you fill template placeholders with specific values using find-and-replace.

Instructions

Find and replace text across all slides (or only some), e.g. fill {{placeholders}} in a template deck.

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>",
      "replacements": "<replacements>"
    },
    "name": "slides_replace_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlySlideIdsNo
replacementsYes
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 safety profile is covered. The description adds the scoping behavior (all slides vs. a subset) but says nothing about unrecoverability of the edit, what happens when a 'find' string is absent, or whether replacements are applied once or iteratively. That silence matters for a non-destructive-flagged but still mutating tool.

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 tight sentence with the scope constraint front-loaded and one concrete example appended. Nothing is padding, though the example could have been used to illustrate the matchCase or batch semantics instead of just the template use case.

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 three-parameter mutation tool with annotations covering the safety profile and no output schema, the description is adequate but thin. The main unresolved gap is match behavior — case sensitivity default, batching, and no-match outcomes — which an agent needs to call this correctly on real decks.

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 parameter meaning; it loosely maps 'across all slides (or only some)' to onlySlideIds and 'find and replace' to replacements. It omits the notable defaults and structures the schema leaves bare: matchCase defaults to true, replacements is a batch array requiring at least one entry with both find and replace, and there is no note on literal vs. regex matching.

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 opens with a specific verb+resource pair, 'Find and replace text across all slides', which clearly identifies the operation and its surface. It also scopes the operation to all slides or a subset, distinguishing it in spirit from sibling mutators like slides_set_text and slides_batch_update, 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?

Usage is only implied: 'e.g. fill {{placeholders}} in a template deck' sketches one scenario, but there is no statement of when to pick this over slides_set_text, slides_batch_update, or docs_replace_text for a Docs target. An agent gets a hint, not a routing rule.

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