Skip to main content
Glama

Create a presentation

create_presentation

Creates a new editable GlideDeck project from a template and returns its slides with element IDs and placeholder text, so you can start or customize a presentation.

Instructions

Creates a new GlideDeck project file from a template (default 'blank') and returns its slides with every element id and placeholder text. The file is a regular GlideDeck project the user can open and edit later.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
pathYesThe GlideDeck project file (.glide.json). Absolute, or relative to the server's folder; `.glide.json` is added when there is no extension.
themeNoTheme name from `catalog`. Prefer the house style, "darkroom" (or "daylight" for a light deck), unless the user asks for another look. Without it a blank deck uses Darkroom and a template keeps its own theme.
titleNo
templateNoTemplate id from `catalog`, e.g. pitch-deck, roadmap, orbit, journey, blank.
overwriteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / theme / description
      Previous value: -"Optional theme name from `catalog` (overrides the template's)."New value: +"Theme name from `catalog`. Prefer the house style, \"darkroom\" (or \"daylight\" for a light deck), unless the user asks for another look. Without it a blank deck uses Darkroom and a template keeps its own theme."
  2. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already mark this as a non-read-only, non-open-world write, so the safety profile is covered. The description adds genuine context by saying the resulting file is a normal project the user can open and edit later, but it says nothing about what happens when the path already exists and overwrite is false, which is the main failure mode for a write 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?

Two compact sentences, front-loaded with the action and immediately followed by the return contract and persistence note. No filler or redundancy.

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

Completeness3/5

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

With no output schema, the description usefully explains what is returned and that the file persists, and it supplies the template default. However, for a five-parameter write tool it leaves overwrite behavior, conflict errors, and the theme-vs-template interaction unaddressed.

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

Parameters2/5

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

At 60% schema coverage, description should carry more weight. It only contributes the 'blank' default for template, which the schema omits; title and overwrite are undocumented in both places, and theme/path meaning comes entirely from the 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 states a specific verb and resource ('Creates a new GlideDeck project file'), names the template default, and discloses the return payload (slides with element ids and placeholder text). This makes clear it is a creation tool rather than a reader like get_presentation, though it never names a sibling explicitly.

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?

There is no when-to-use or when-not-to-use guidance: nothing tells the agent to call this instead of import_pptx or get_presentation, nor when to pick a template over 'blank'. The only hint is the parenthetical default, which is a fallback value rather than guidance.

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