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

office-powerpoint-mcp-server

Manage Slides

manage_slides

Add, duplicate, delete, reorder, or populate PowerPoint slide placeholders to restructure presentations and insert text content.

Instructions

Perform slide structural operations: duplicate, delete, reorder, or populate placeholders.

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_slides"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText content to insert into placeholder
actionYesSlide structural action: add, duplicate, delete, reorder, populate_placeholder
to_indexNoTarget destination index (required for 'reorder')
auto_saveNoWhether to automatically save changes to file_path on disk
file_pathNoPath to presentation file within sandbox
slide_indexNo0-based index of target slide
layout_indexNoLayout index for 'add' action (default 6 for blank layout)
presentation_idNoIn-memory presentation ID
placeholder_nameNoPlaceholder name / title for 'populate_placeholder'
placeholder_indexNoPlaceholder index for 'populate_placeholder'

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, but the description advertises a 'delete' operation that removes a slide, which is inherently destructive – a mismatch the agent should be warned about rather than left to infer. The description also omits relevant side effects it could disclose, such as auto_save defaulting to true (changes written to file_path on disk) and that operations mutate an in-memory presentation identified by presentation_id.

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 compact sentence with the operation list front-loaded and no filler. Its brevity is not achieved through under-specification of behavior, though the omitted 'add' action makes the list inaccurate rather than merely short.

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?

This is a 10-parameter, multi-action mutation tool, and the description supplies no per-action parameter guidance, no note about auto_save/file_path disk writes, and no indication of what happens to slide indices after delete/reorder. The output schema covers return values, but the action selection and side-effect picture remain 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?

Schema description coverage is 100%, so every parameter is already documented in the schema, and the baseline is 3. The description adds nothing about which parameters apply to which action (e.g., to_index only for reorder, layout_index only for add), leaving that mapping entirely to the schema.

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?

Names a specific verb family (structural operations) and resource (slides), and enumerates duplicate/delete/reorder/populate placeholders. However, the enumeration omits 'add', which is the first value of the action enum in the schema, so an agent reading only the description would not know the tool can add slides.

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 when-to-use or when-not-to-use guidance. It does not say how this differs from siblings such as add_slide_from_template, add_bullet_slide, or manage_presentation, nor which action to pick for a given goal (e.g., inserting a new slide vs. duplicating an existing one).

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