Skip to main content
Glama
Sign In
gg-mcp

gg-mcp

by tannht
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

add_text_to_slide

Add a text box to a specific slide in Google Slides. Specify the presentation, slide index, text content, and optional position and size.

Instructions

Add a text box to a slide. slide_index: 0-based. Coordinates in points (pt).

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": {
      "presentation_id": "<presentation_id>",
      "slide_index": "<slide_index>",
      "text": "<text>"
    },
    "name": "add_text_to_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
presentation_idYes
slide_indexYes
textYes
xNo
yNo
widthNo
heightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It provides some behavioral info (0-based index, points as units) but omits crucial details like whether text is appended, position behavior, or authentication needs.

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 sentences, front-loaded with the action. No fluff, but could add more value without sacrificing conciseness.

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?

Given 7 parameters, no output schema, and no annotations, the description is incomplete. It lacks return value info, error scenarios, and details on how to position text boxes correctly.

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 0%. The description adds meaning for slide_index (0-based) and coordinates (points), but does not explain presentation_id, text, width, height, or the effect of defaults. Insufficient for 7 parameters.

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 clearly states 'Add a text box to a slide', which is a specific verb+resource. It adds coordinate and indexing details but does not differentiate from sibling tools like 'add_slide' or 'delete_slide', though those are distinct actions.

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 tool or when to avoid it. No mention of alternatives or prerequisites. The description only states what it does, not when it's appropriate.

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

Deploy Server

Other Tools