Skip to main content
Glama

pptx_reorder_slides

Reorder slides in a PowerPoint file by moving a slide from its current index to a specified destination index.

Instructions

Move a slide from one position to another.

This is a true move: the slide at from_index is removed first, then inserted at to_index in the resulting sequence (VAL-PPTX-027). So moving slide 0 to position 2 in a 3-slide deck [A, B, C] yields [B, C, A], not the swap result [C, B, A].

Reordering a slide to its own index (from_index == to_index) is a no-op that still returns {"ok": True} (VAL-PPTX-028).

Args: path: Path to an existing .pptx. from_index: 0-based index of the slide to move. to_index: 0-based destination index. Must satisfy 0 <= to_index < slide_count (after the slide is removed from from_index). folder: Optional base folder for relative paths.

Returns: {"ok": True}.

Raises: OfficeMCPError: ERR_INVALID_PARAMS for a non-int or out-of-range from_index / to_index, in which case the deck is left unchanged (VAL-PPTX-029); ERR_FILE_NOT_FOUND if the file is missing; ERR_UNSUPPORTED_FMT for non-.pptx extensions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
from_indexYes
to_indexYes
folderNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations are provided, so the description carries full burden. It fully discloses the true move semantics, no-op behavior, error handling (returns error without modifying deck), and specific validation rules.

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 fairly long but well-structured with clear sections (description, example, args, returns, raises). Each sentence adds value, though some verbosity could be trimmed. Still appropriately sized for the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (non-trivial index logic) and absence of annotations, the description covers behavior, parameter details, return format, and error cases thoroughly. It is complete and self-contained for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, meaning no parameter descriptions in the schema. The description compensates by explaining each parameter: path, from_index, to_index with range constraint after removal, and folder as optional. This adds significant meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it moves a slide from one position to another, using the verb 'move' and resource 'slide'. It explicitly distinguishes the move from a swap with a concrete example, differentiating it from sibling tools like pptx_delete_slide or pptx_add_slide.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides detailed guidance on how to use the tool, including index behavior (0-based, after removal) and no-op for same index. However, it does not explicitly state when to use this tool over alternatives, but the contrast with swap is implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gawirable/office-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server