Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

slides_add_text_box

Adds a text box to a Google Slides slide at a specified position and size in points, enabling custom text placement.

Instructions

Add a text box to a slide. Position/size in points.

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>",
      "slide": "<slide>",
      "text": "<text>"
    },
    "name": "slides_add_text_box"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
boldNo
textYes
slideYesSlide objectId, or 1-based slide number
widthNo
heightNo
fontSizeNo
presentationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.7/5.0
Behavior2/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 safety is largely covered. However, the description says nothing beyond the write itself: no note on whether the new box is layered on top of existing elements, whether it is added to the current slide revision, or what the caller gets back. For a 9-parameter mutation tool, that is thin.

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?

Two terse sentences with the action front-loaded and no wasted wording. The telegraphic second sentence is efficient but borders on under-specified.

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

Completeness2/5

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

Nine parameters, three required, near-zero schema coverage, no output schema, and an open-world mutation hint. Given that complexity, the definition leaves too much implicit about geometry semantics, defaults, and the result of the call.

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

Parameters2/5

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

Schema description coverage is only 11% — only `slide` is documented — so the description must compensate. "Position/size in points" usefully supplies units for x, y, width and height, which the schema lacks, but it says nothing about fontSize units, bold behavior, or the default placement when coordinates are omitted.

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?

States a specific verb and resource ("Add a text box to a slide") plus a scoping detail about positioning. It is clearly distinct from siblings like slides_add_image or slides_replace_text, though it does not name 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 Guidelines2/5

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

No guidance on when to use this versus slides_replace_text, slides_set_text, or slides_add_image, and no prerequisites (e.g., that the presentation and slide must already exist). The caller must infer everything from the name.

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