Skip to main content
Glama

pptx_add_slide

Append a new slide to an existing PowerPoint file. Set layout by index and optionally populate the title placeholder.

Instructions

Append a new slide to the deck.

The slide is always appended to the end (VAL-PPTX-018 — the returned index equals the previous slide count). When title is given, the slide's title placeholder is populated (VAL-PPTX-021).

Args: path: Path to an existing .pptx. layout_index: 0-based index into prs.slide_layouts. The default 1 is the "Title and Content" layout in python-pptx's default template. title: Optional title text. When None the title placeholder is left empty. folder: Optional base folder for relative paths.

Returns: {"index": <int>} — the 0-based index of the new slide.

Raises: OfficeMCPError: ERR_INVALID_PARAMS for a non-int or out-of-range layout_index (the deck is not modified in this case — VAL-PPTX-020), ERR_FILE_NOT_FOUND if the file is missing, ERR_UNSUPPORTED_FMT for non-.pptx extensions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
layout_indexNo
titleNo
folderNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/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 discloses that slides are always appended, the returned index equals previous count, title populates placeholder, and errors like out-of-range layout_index do not modify the deck. This is comprehensive for behavioral transparency.

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 structured with sections for args, returns, raises, and behavioral notes. It is slightly verbose but every sentence is informative. No fluff.

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 no schema coverage and no output schema, the description fully covers parameters, return value, and error conditions. It also includes behavioral details like VAL-PPTX-018 and VAL-PPTX-021. Complete for this tool's complexity.

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

Parameters4/5

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

Schema coverage is 0%, so description must add meaning. It explains each parameter: path is path to .pptx, layout_index is 0-based with default 1 being 'Title and Content', title optional, folder optional. This adds significant value 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 the tool appends a new slide to the deck, distinguishing it from other pptx_add_* siblings. The verb 'Append' and resource 'slide' are specific.

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?

The description explains what the tool does but does not explicitly guide when to use this tool versus alternatives like pptx_add_shape or pptx_add_table. Usage context is implied but no exclusions or alternatives are mentioned.

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