Skip to main content
Glama
Sign In
PptxGenJS MCP Server

PptxGenJS MCP Server

by Hrithik-s-Raj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_text

Add text to a slide in a PowerPoint presentation, with options to set font size, color, bold, italic, alignment, and position.

Instructions

Add text to a slide with various formatting options.

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>",
      "slideNumber": "<slideNumber>",
      "text": "<text>"
    },
    "name": "add_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
hNoHeight in inches (default: 1)
wNoWidth in inches (default: 8)
xNoX position in inches (default: 1)
yNoY position in inches (default: 1)
boldNoBold text
textYesThe text content to add
alignNoText alignment (left, center, right, justify)
colorNoText color (hex format like '363636')
italicNoItalic text
fontSizeNoFont size in points (default: 18)
slideNumberYesSlide number (1-based index)
presentationIdYesThe ID of the presentation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only mentions 'various formatting options.' It does not explain side effects, whether text is added to an existing slide or creates a new element, or any positioning behavior, leaving significant gaps for a mutation 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?

The description is a single, efficient sentence with no filler. It is concise and front-loaded, though it could include more useful detail without becoming verbose, so it misses a perfect score.

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?

For a tool with 12 parameters and no output schema, the description is too minimal. It does not explain coordinate systems, default behavior, or that it modifies an existing presentation. The schema explains individual parameters, but the overall usage context is incomplete.

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?

The input schema provides descriptions for 100% of the parameters, so the schema carries the full burden of explaining parameters. The description's mention of 'formatting options' adds marginal context beyond the schema, so baseline 3 is appropriate.

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 the action ('Add text') and the target ('to a slide'), making its purpose obvious. It indirectly differentiates from sibling tools like add_shape or add_image by focusing on text, but it does not explicitly name alternatives.

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?

There is no guidance on when to use this tool versus alternatives such as add_shape or add_table. The description implies use for adding text but provides no contextual prerequisites or exclusions.

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