PptxGenJS MCP Server

create_presentation

Creates a new PowerPoint presentation and returns a presentation ID for all subsequent operations like editing slides or exporting.

Instructions

Create a new PowerPoint presentation. Returns a presentation ID that should be used for all subsequent operations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_presentation"
  }
}

Input Schema

Name	Required	Description
`id`	No	Optional custom ID for the presentation. If not provided, one will be generated.
`title`	No	Title of the presentation
`author`	No	Author name
`company`	No	Company name
`subject`	No	Subject of the presentation

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It adds the behavioral detail of returning a presentation ID for later use, which is valuable. However, it doesn't disclose potential side effects, permissions, persistence, or error handling, leaving gaps for a creation tool.

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 a single, front-loaded sentence with no redundant words. It clearly states the core action and follows with the key return-value usage instruction.

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?

For a simple creation tool with a fully documented schema and clear sibling relationships, the description is sufficient. It explains the returned ID and how to use it in subsequent operations. Lacking annotations, it doesn't cover edge cases or authorization, so it's not a 5.

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 schema description coverage is 100%, so each parameter is already fully documented. The description adds no additional parameter-specific guidance, so a baseline score of 3 is appropriate.

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 uses a specific verb 'create' with a clear resource 'PowerPoint presentation', distinguishing it from sibling tools like add_slide or delete_presentation. It also mentions the return value, which further clarifies its role.

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 phrase 'should be used for all subsequent operations' clearly implies this is the initial step for working with presentations, providing contextual guidance. It doesn't explicitly exclude alternatives, but the sibling list makes the tool's entry-point role obvious.

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

Deploy Server