Skip to main content
Glama
photonn

dial-pptx-mcp

by photonn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_presentation_from_template_content

Generate a new PowerPoint deck from a .pptx template, preserving its theme, layouts, and branding. Provide template content and optional markdown instructions to obtain a presentation_id for subsequent edits.

Instructions

Create a new presentation from an uploaded .pptx template file.

A PowerPoint 97-2003 (.ppt) file is accepted too and converted to .pptx on the way in, where the server has LibreOffice.

template_content: the .pptx/.potx/.ppt template file content, as a data: URI or a base64-encoded string (in DIAL Quick Apps, pass the template file as file:data::files/{bucket}/{path} and it is resolved automatically).

instructions_content: optional — the template's own build instructions, a markdown (.md) file stored beside the template and passed the same way (file:data::files/{bucket}/{path}). Pass it whenever the template has one: it carries the rules for this specific template (which slide to use for what, the accent colour, what the footer must say) that no generic guidance can know. If the file does not exist, omit this argument — the template loads exactly as before.

The template's theme, layouts, masters and branding are preserved. Returns a presentation_id that must be passed to all subsequent tool calls for this deck, and, when instructions were supplied, their section list — read them with get_template_instructions before planning the deck.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
template_contentYes
instructions_contentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.9.0
    • addedInput schema / properties / instructions_content
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Instructions Content"
+}
  2. First observedv2.6.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations are minimal (only a title), so the description carries the behavioral burden. It discloses that the template's theme/layouts/masters are preserved, that .ppt files are converted to .pptx if LibreOffice is available, and that the tool returns a presentation_id and section list when instructions are provided. It does not cover error cases or side effects, but the disclosed behavior is valuable and not contradicted by annotations.

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 well-structured with the core purpose front-loaded, followed by parameter details and behavioral notes. Every sentence serves a purpose, and it is appropriately sized for a tool with two parameters and nuanced usage.

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?

For a tool with two parameters (one optional) and an output schema, the description covers all essential aspects: how to pass files, when to include instructions, what is preserved, and what is returned. It even directs reading instructions via get_template_instructions. Nothing critical is missing.

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?

Schema description coverage is 0%, so the description fully compensates. It explains template_content as a data URI, base64 string, or DIAL file reference, and instructions_content with detailed guidance on when to pass it and what it contains. This adds substantial meaning beyond the bare schema.

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 creates a new presentation from an uploaded .pptx template file, with specific details about accepted formats and conversion. It is a clear verb+resource, but does not explicitly distinguish it from siblings like create_presentation_from_template or create_presentation_from_templates.

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 gives context on when to use the tool (creating from a template file) and detailed guidance on when to pass the optional instructions_content parameter. However, it never mentions alternatives or when not to use this tool versus similar siblings, so usage guidance is implied but not explicit.

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

Deploy Server

Other Tools