Skip to main content
Glama

PowerPoint Presentation Creator

create_powerpoint_presentation

Creates PowerPoint presentations from structured slide objects, supporting various slide types including titles, content, tables, images, charts, and quotes.

Instructions

Creates PowerPoint presentations from structured slides.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoAspect ratio: '16:9' (widescreen) or '4:3' (traditional)16:9
slidesYesList of slide objects. Each slide requires 'slide_type' (str) and type-specific fields: - title: {slide_type: "title", slide_title: str, author?: str} - section: {slide_type: "section", slide_title: str} - content: {slide_type: "content", slide_title: str, slide_text: [{text: str, indentation_level: int (1-3)}]} - table: {slide_type: "table", slide_title: str, table_data: [[str]] (first row = header), header_color?: str (hex), alternate_rows?: bool} - image: {slide_type: "image", slide_title?: str, image_url: str, image_caption?: str} - two_column: {slide_type: "two_column", slide_title: str, left_column: [{text: str, indentation_level: int}], right_column: [{text: str, indentation_level: int}], left_heading?: str, right_heading?: str} - chart: {slide_type: "chart", slide_title: str, chart_type: str (bar|column|line|pie|doughnut|stacked_bar|area), chart_data: {categories: [str], series: [{name: str, values: [number]}]}, has_legend?: bool, legend_position?: str} - quote: {slide_type: "quote", slide_title?: str, quote_text: str, quote_author?: str} All slides support optional 'speaker_notes': str field.
file_nameNoCustom filename for the output file (without extension). If not provided, a unique identifier will be used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations lack readOnlyHint or destructiveHint, so the description carries the full burden. It does not disclose whether the tool overwrites existing files, requires authentication, or has rate limits.

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 a single sentence, front-loaded with the main purpose. It is concise but could include more context without becoming verbose.

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

Completeness2/5

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

Despite rich input schema and output schema present, the description lacks examples, edge cases, or guidance for complex slide types. It does not fully compensate for the tool's complexity.

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 baseline is 3. The description adds minimal value beyond the schema, essentially restating 'from structured slides' without elaborating on parameters like file_name or format.

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 'Creates PowerPoint presentations from structured slides,' which is a specific verb+resource. However, it does not differentiate from sibling tools like render_pptx_template that also create PPTX files.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as render_pptx_template or duplicate_pptx_slide. Also missing are prerequisites, limitations, or typical use cases.

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/filhocf/docforge-mcp'

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