Skip to main content
Glama
Sign In

Clipia

by io.github.clipia-ai
OverviewDiscussionsAdmin

generate_presentation

Generate a BRAND-NEW slide presentation (editable PPTX + PDF + PNG previews) from a DeckSpec you compose. To change a deck that already exists (slide text, title, theme, add/remove/reorder slides) use edit_presentation instead — it reuses the illustrations already generated instead of billing them again. Returns request_id (prs_*) — poll with wait_generation until COMPLETED, then output has pptx_url, pdf_url, preview_urls[]. Write the full spec: title, language (ru/en), theme, optional brand, and 3–20 slides. ALWAYS pick the theme that fits the SUBJECT of the deck; the deck belongs to the user, so never default to the Clipia brand palette unless the deck is about Clipia itself. Set brand.name/brand.website only if the user names their company — otherwise slides stay unbranded. Each slide has a "layout": cover, section, bullets, two-col, image-full, quote, stats, or closing. For illustrations set image.prompt (English) — generated by our image models and billed as credits; skip images for text-only slides. Costs credits (render fee + illustrations).

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": {
      "title": "<title>",
      "slides": "<slides>"
    },
    "name": "generate_presentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoPresenter's own branding (footer + closing slide). Set ONLY if the user names their company/site; omit for unbranded decks (default).
themeNoVisual theme — pick the one that fits the SUBJECT of the deck. Dark: midnight (neutral graphite/blue, default), slate (indigo — tech, product, startup), noir (black/gold — luxury, real estate, investment), forest (green — ecology, agriculture, health), ember (warm orange — travel, food, sport, energy). Light, for print/projector: paper (neutral white — office, academic), ivory (warm terracotta — lifestyle, travel, hospitality), azure (cool blue — corporate, finance, consulting). clipia-dark / clean-light are the Clipia brand palettes — use ONLY for decks about Clipia itself.
titleYesCover title.
slidesYesSlides in order (3–20).
languageNoContent language (default ru). Write slide text in it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent, closed-world write operation. The description adds crucial behavioral context beyond that: credit costs for rendering and illustrations, async request_id polling via wait_generation, and the returned URL fields.

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 purpose and sibling routing are front-loaded, and most sentences carry actionable information. It is dense and appropriately sized for a complex nested tool, though billing is mentioned several times and the single-paragraph structure could be tighter for such a long spec.

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?

The description covers creation flow, cost implications, polling behavior, return fields, branding defaults, theme selection, slide layouts, and image-generation billing. For a complex 5-parameter nested tool with no output schema, that is complete enough for an agent to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents theme, brand, language, and layout semantics in detail. The description reinforces practical guidance such as picking themes by subject and skipping images for text-only slides, though much of the parameter detail duplicates the schema rather than adding new meaning.

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?

States a specific verb and resource: generate a BRAND-NEW slide presentation with PPTX, PDF, and PNG outputs from a DeckSpec. It immediately distinguishes itself from edit_presentation, so an agent can tell which tool creates versus modifies a deck without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says to use edit_presentation for existing decks and explains why (it reuses illustrations instead of billing again). It also names wait_generation for polling, giving the agent a complete routing path for creation, editing, and async completion.

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

All Clipia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources