Skip to main content
Glama
rcarmo

office-document-mcp-server

by rcarmo

pptx_delete_slide

Destructive

Remove a specific slide from a PowerPoint file by providing its slide number. Use it to delete unwanted or template slides from presentations.

Instructions

Remove a slide from the presentation.

USE THIS to remove template slides you don't need or to clean up unwanted content.

Args: file_path: Path to the .pptx file slide_number: 1-based slide number to delete output_path: Optional output path (defaults to overwriting input)

Returns: Status with remaining slide count

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to the .pptx file
slide_numberYes1-based slide number to delete
output_pathNoOptional output path (defaults to overwriting input)
Behavior4/5

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

Annotations show destructiveHint=true. Description adds that output defaults to overwriting input and returns status with remaining count, providing useful behavioral context beyond annotations.

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?

Description is well-structured with a front-loaded purpose sentence and a clear Args section. Appropriate length for the tool's simplicity.

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

Completeness4/5

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

Covers main behaviors: deletion, default overwrite, return value. No output schema, but return described. Adequate for a simple deletion 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 coverage is 100%, so description doesn't need to add much. It repeats parameter descriptions from schema and adds default for output_path, but adds minimal new meaning.

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?

Description clearly states 'Remove a slide from the presentation.' with a specific verb and resource. Siblings like pptx_add_slide and pptx_duplicate_slide indicate distinct actions.

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?

Explicitly says 'USE THIS to remove template slides you don't need or to clean up unwanted content.' Provides context for when to use, though no explicit when-not or comparison to siblings.

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/rcarmo/python-office-mcp-server'

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