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

office-powerpoint-mcp-server

Manage Presentation

manage_presentation

Create, open, save, close, or configure PowerPoint presentations, including slide size and document properties, with in-memory sessions or disk auto-saving.

Instructions

Create, open, save, close, or configure PowerPoint presentations.

Defaults to widescreen 16:9 format (13.333 x 7.5 inches). Supports hybrid in-memory sessions and direct disk auto-saving.

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

Input Schema

NameRequiredDescriptionDefault
titleNoDocument core title property
actionYesLifecycle action to perform on presentation
authorNoDocument core author / creator property
commentsNoDocument core comments / description property
auto_saveNoWhether to automatically persist changes to file_path on disk
file_pathNoFile path within allowed directory sandbox
width_inchesNoSlide width in inches (default: 13.333 for widescreen 16:9)
height_inchesNoSlide height in inches (default: 7.5 for widescreen 16:9)
presentation_idNoUnique ID for in-memory presentation session

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: default 16:9 dimensions and the existence of both in-memory sessions and disk auto-saving. It still omits consequential behavior such as whether 'close' discards unsaved changes or whether 'create' overwrites an existing file_path, which matters for a non-idempotent 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?

Three short lines, front-loaded with the action list followed by defaults and session behavior; nothing is padded. The dimension defaults sentence largely duplicates schema defaults, so it earns slightly less than full marks.

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 nine parameters, one required, and an output schema that handles return values, the description is complete on the surface but thin for a multi-action tool: it never says which parameters apply to which action (title/author for create or set_properties, presentation_id for save/close, file_path for auto_save). That is the main remaining gap an agent would want filled.

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 the schema already documents every parameter including defaults. The description restates the widescreen defaults (13.333 x 7.5) and gestures at auto_save and in-memory sessions, but adds no action-to-parameter mapping, which is the piece the schema cannot express on its own.

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 an explicit verb list (create, open, save, close, configure) bound to a specific resource (PowerPoint presentations), which maps directly onto the action enum. It is clear what the tool does, though it never states how it differs from siblings like manage_slides or inspect_presentation, leaving the lifecycle-vs-content distinction implicit.

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 implied by the enumerated lifecycle actions, and the note about hybrid in-memory sessions versus disk auto-saving hints at two operating modes. However, there is no explicit when-to-use guidance, no sequencing prerequisites (e.g., that a presentation must be created/opened before other tools act on it), and no mention of alternatives among the siblings.

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