Skip to main content
Glama
office-powerpoint-mcp-server

office-powerpoint-mcp-server

Manage Text

manage_text

Add, update, or clear text boxes and multi-level bulleted lists on PowerPoint slides, with automatic font scaling to prevent text overflow.

Instructions

Add, update, or clear text boxes and multi-level bulleted lists.

Features:

  • Multi-level indentation (levels 0-4)

  • Run-level bold, color, and size overrides

  • Automatic shrink-to-fit font scaling preventing box overflow

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": {
      "slide_index": "<slide_index>",
      "action": "<action>"
    },
    "name": "manage_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoTop coordinate in inches (for 'add')
boldNoWhether text is bold
leftNoLeft coordinate in inches (for 'add')
textNoPlain text content or single paragraph
widthNoWidth in inches (for 'add')
actionYesText action: 'add' (creates text box), 'update' (modifies shape), 'clear'
heightNoHeight in inches (for 'add')
italicNoWhether text is italic
auto_fitNoAutomatically scale down font size based on character count
alignmentNoText horizontal alignment: left, center, right, justifyleft
auto_saveNoWhether to automatically save changes to file_path on disk
file_pathNoPath to presentation file within sandbox
font_nameNoFont family name (e.g. 'Helvetica', 'Arial')Arial
font_sizeNoFont size in points (auto-fit if omitted and auto_fit=True)
font_colorNoHex font color e.g. '#1A1A1A'#1A1A1A
shape_indexNoShape index to update or clear (required for update/clear)
slide_indexYes0-based index of slide
bullet_pointsNoMulti-level bullet points or nested items
presentation_idNoIn-memory presentation ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false. The description adds genuinely new behavior: auto shrink-to-fit font scaling that prevents box overflow, level 0-4 indentation, and run-level bold/color/size overrides. It omits two things an agent would want: that auto_save (default true) writes to disk, and that 'clear' destroys existing text content.

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 lead sentence followed by three short feature bullets; the primary action statement is front-loaded and no sentence is filler. The feature list is slightly redundant with the schema but stays cheap.

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?

With an output schema present and full parameter documentation, the description only needs to carry action semantics and side effects. It covers the feature surface but leaves the add-vs-update-vs-clear workflow and the auto-save write behavior unstated for a 19-parameter mutation tool.

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 100%, so every one of the 19 parameters is already documented in the schema. The description's feature bullets (levels 0-4, auto-fit, run-level overrides) restate what the schema already declares rather than adding format or precedence rules.

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 concrete verb triple (add/update/clear) and a specific resource (text boxes and multi-level bulleted lists), which lets an agent tell it apart from shape, image, chart and table tools. It stops short of naming the nearest sibling, manage_shapes, so the boundary between 'a text box' and 'a shape' is left implicit.

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 when-to-use guidance, no prerequisites, and no alternatives named. The three actions are enumerated but the description does not state that 'update'/'clear' require an existing shape_index while 'add' requires coordinates, nor when an agent should reach for this tool over manage_shapes.

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