Skip to main content
Glama

pptx_create_presentation

Create a new PowerPoint .pptx file, optionally with a title slide. Specify the file path and an optional title to generate a presentation with a title slide.

Instructions

Create a new .pptx file at path, optionally with a title slide.

Args: path: Target .pptx path. May be absolute or relative to folder (or to the default folder when folder is None). title: Optional text for the first slide's title placeholder. When None (the default), the file is created with no slides at all (VAL-PPTX-002). When a non-empty title is given, a single slide is appended using the "Title Slide" layout (index 0) and the title is written into its title placeholder (VAL-PPTX-001). folder: Optional base folder for relative paths.

Returns: {"path": "<absolute path>"}.

Raises: OfficeMCPError: ERR_INVALID_PARAMS if path is empty or a file already exists at the target, ERR_UNSUPPORTED_FMT if path does not end in .pptx.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
titleNo
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 provided, description carries full burden. Discloses error conditions (empty path, existing file, unsupported format), return value, and slide creation logic. Fully transparent.

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?

Well-structured with Args/Returns/Raises, but includes internal error codes (VAL-PPTX-001) that may add noise. Could be slightly more concise.

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?

With output schema present, description covers return value, all parameters, and errors. No gaps for a creation tool.

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?

Input schema has 0% description coverage; description compensates by detailing path (absolute/relative), title (None vs non-empty), and folder as base for relative paths.

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?

Clearly states it creates a new .pptx file, optionally with a title slide. Differentiates from siblings like pptx_add_slide which modify existing presentations.

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?

Explains behavior of title parameter (when to create slide vs no slides). Implicitly differentiated from siblings, but lacks explicit 'use this for creation, use pptx_add_slide for adding slides'.

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