Powerpoint MCP Server

Overview Schema Source Related Servers Discussions Admin

save-presentation

Save PowerPoint presentations to files after creating or editing slides. Use this tool to store your presentation work permanently.

Instructions

Save the presentation to a file. Always use this tool at the end of any process that has added slides to a presentation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`presentation_name`	Yes	Name of the presentation to save
`output_path`	No	Path where to save the presentation (optional)

Implementation Reference

src/powerpoint/server.py:649-678 (handler)

Handler for the 'save-presentation' tool. Retrieves the in-memory presentation object, determines the output file path (defaulting to presentation_name.pptx), saves it using python-pptx Presentation.save(), handles errors, and returns a text confirmation with the saved path.

elif name == "save-presentation":
    presentation_name = arguments.get("presentation_name")
    output_path = arguments.get("output_path")


    if not presentation_name:
        raise ValueError("Missing presentation name")

    if presentation_name not in presentation_manager.presentations:
        raise ValueError(f"Presentation not found: {presentation_name}")

    prs = presentation_manager.presentations[presentation_name]

    # Default output path if none provided
    if not output_path:
        output_path = f"{presentation_name}.pptx"

    file_path = os.path.join(path,output_path)
    # Save the presentation
    try:
        prs.save(file_path)
    except Exception as e:
        raise ValueError(f"Unable to save the {presentation_name}. Error: {e}")

    return [
        types.TextContent(
            type="text",
            text=f"Saved presentation to: {file_path}"
        )
    ]

src/powerpoint/server.py:343-361 (registration)

Registration of the 'save-presentation' tool in the list_tools handler, including its schema defining required 'presentation_name' and optional 'output_path'.

types.Tool(
    name="save-presentation",
    description="Save the presentation to a file. Always use this tool at the end of any process that has "
                "added slides to a presentation.",
    inputSchema={
        "type": "object",
        "properties": {
            "presentation_name": {
                "type": "string",
                "description": "Name of the presentation to save",
            },
            "output_path": {
                "type": "string",
                "description": "Path where to save the presentation (optional)",
            },
        },
        "required": ["presentation_name"],
    },
),

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

A3.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool saves to a file but lacks details on permissions, file formats, error handling, or whether it overwrites existing files. For a write operation tool, this leaves significant behavioral gaps, though it does imply it's for finalizing changes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is highly concise and front-loaded, with two sentences that directly convey purpose and usage without any wasted words. Each sentence earns its place by providing essential information, making it efficient and well-structured.

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?

Given the tool's complexity (a write operation with 2 parameters), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose and usage but lacks details on behavioral traits, output, or error handling, leaving gaps that could hinder an agent's effective use.

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?

The input schema has 100% description coverage, documenting both parameters clearly. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Thus, it meets the baseline of 3, as the schema does the heavy lifting.

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 clearly states the tool's purpose with a specific verb ('Save') and resource ('presentation to a file'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'generate-and-save-image' or 'create-presentation', which might involve saving operations in different contexts, leaving room for minor ambiguity.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: 'Always use this tool at the end of any process that has added slides to a presentation.' This clearly indicates when to use it (after slide additions) and implies when not to use it (e.g., at the start or without changes), offering strong contextual direction.

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

Deploy Server