Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
api_keyYesYour Presentations.AI API key from https://presentations.ai/dashboard

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_presentation_from_topicA

Generate a full AI-powered presentation from a topic or brief. Use when the caller has a subject line, headline, or short brief and wants a complete deck. Returns a job ID for async processing; poll check_job_status until status is completed, then use the returned docurl. For a single hero slide instead of a deck, use create_single_slide.

create_single_slideA

Generate a single AI-designed slide from a topic. Use for hero slides, social-media graphics, or one-off visuals. For a full multi-slide deck, use create_presentation_from_topic. Returns a job ID; poll check_job_status until status is completed. Faster than full-deck generation (typically 20-40 seconds).

create_presentation_from_contentA

Transform raw text (articles, notes, transcripts, reports, outlines) into a polished presentation. Use when the caller has prose or notes already and wants a deck built from that source material. Honor preservationMode: 'preserve' keeps the structure and auto-counts slides, 'enhance' rewrites for clarity, 'summarize' condenses, 'instruction' uses topic as a directive. For file uploads (PDF/DOCX/PPTX) use create_presentation_from_file. Returns a job ID; poll check_job_status.

create_presentation_from_fileA

Convert an uploaded document (PDF, Word, PowerPoint, plain text, markdown, RTF) into a presentation. Use when the caller already has a source document. Max 5 MB after base64 encoding. Supports the same preservation modes as create_presentation_from_content. For pasted raw text use create_presentation_from_content. Returns a job ID; poll check_job_status.

check_job_statusA

Poll for the result of an async presentation job. Use after any create_* call that returned a jobId. Safe to call repeatedly; does not consume job state. Recommended cadence: wait 55-60 seconds before the first poll, then every 30-35 seconds. Most jobs complete within 2 minutes. When status is 'completed', the response includes docurl (viewer link), docid (numeric ID), and optionally animated_url and thumbnailUrl. When status is 'failed', the response includes an error field. While 'processing', keep polling.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.7/5.0

Scored across 5 tools

Disambiguation5/5

Each creation tool has a distinct input type (raw text, file, topic, single slide) with explicit cross-references in descriptions, making selection unambiguous. The polling tool is clearly separate and serves all creation tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (check_job_status, create_presentation_from_content, etc.), with verbs 'check' and 'create' and nouns describing the input or target.

Tool Count5/5

Five tools cover all essential creation pathways (content, file, topic, single slide) plus async polling, which is well-scoped for a presentation generation server without unnecessary bloat.

Completeness5/5

The set provides complete coverage for generating presentations from various sources and checking results. No obvious gaps exist for its stated purpose of AI-powered presentation creation.

Maintenance

ActivityInactive
ResponsivenessUnresponsive