SlideForge

Create Multi-Slide Deck

create_deck

Create a complete PowerPoint presentation (.pptx): a whole multi-slide deck, native and editable, in one call. slides is a list of create_slide intents (same form menu + data shapes — see create_slide). Slides fill in parallel and merge into one themed PPTX with page numbers. Include furniture: a hero_statement cover, section_divider breaks, and a closing (hero_statement variant=contact_closing via blocks-free slots).

BLOCKED ($0)? If an error has can_autofix:true, merge its patch into the args at patch_target. Unchanged retries repeat the block. New form: browse_catalog(type=schema) first.

Also: mode=assemble merges existing slide job_ids as-rendered (free; theme_id does NOT re-theme them — render with create_deck(slides=[…], theme_id=…) for a unified theme); mode=fork clones a deck (free). Polling: deck_id == job_id — manage_account(action=job, job_id=).

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No	Default render. assemble/fork are free deck plumbing.
`name`	No
`title`	No	Deck title (PowerPoint metadata)
`slides`	No	each item is a create_slide intent (same form menu, typed fields, and data shapes as create_slide).
`deck_id`	No	Existing deck ID (for mode=fork, or mode=render to update)
`dry_run`	No	Deck-level free pre-flight (cost:0, NO render/PPTX): returns a per-slide validation manifest [{i, form, fidelity_forecast, status, errors}] so you can fix bad slides before spending. A deck is one artifact, so validation is all-or-nothing — put dry_run here, not on individual slides. Resend without dry_run to render.
`imagery`	No	Deck-level imagery mode, inherited by every slide (a slide-level imagery wins). See create_slide.imagery.
`job_ids`	No	Slide job IDs to merge (for mode=assemble)
`logo_id`	No	Optional brand logo (from upload_asset purpose=logo) applied as chrome to every content slide in the deck.
`styling`	No	Deck-level topical-design switch, inherited by every slide (a slide-level styling wins). See create_slide.styling.
`language`	No	ISO 639-1 (default en) for every slide: furniture labels and authored fills follow it.
`theme_id`	No
`direction`	No	Deck-level writing direction, inherited by every slide (a slide-level direction wins) — set it once for an Arabic/Hebrew deck. Covers/dividers rendered on an UPLOADED brand template keep that template's own layout direction. See create_slide.direction.
`imagery_tag`	No	Deck-level subject declaration, inherited by every slide (a slide-level imagery_tag wins). Declare it once for a whole deck. See create_slide.imagery_tag.
`force_render`	No	IGNORED (deck-level). pptx_url is always returned when at least one slide rendered, so there is nothing to force. Still meaningful on create_slide.
`allow_partial`	No	IGNORED. A deck bills per rendered slide and always returns its pptx; slides that failed or rendered badly are free and named in repair_actions.
`strict_policy`	No	Optional CI-style gate for automated report pipelines. dry_run returns policy_result; render returns rejected/cost:0 if the policy fails.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 18, 2026

changedInput schema / properties / language / description

Previous value: -"Target language"New value: +"ISO 639-1 (default en) for every slide: furniture labels and authored fills follow it."

changedInput schema / properties / language / enum

Previous value: -[
-  "en",
-  "de",
-  "fr",
-  "es",
-  "it",
-  "pt",
-  "nl",
-  "pl",
-  "ru",
-  "uk"
-]New value: +[
+  "bg",
+  "ca",
+  "cs",
+  "da",
+  "de",
+  "el",
+  "en",
+  "es",
+  "et",
+  "fi",
+  "fr",
+  "gl",
+  "hr",
+  "hu",
+  "id",
+  "is",
+  "it",
+  "ja",
+  "ko",
+  "lt",
+  "lv",
+  "nl",
+  "no",
+  "pl",
+  "pt",
+  "ro",
+  "ru",
+  "sk",
+  "sl",
+  "sr",
+  "sv",
+  "tr",
+  "uk",
+  "vi",
+  "zh"
+]

Changed1 schema field changedAug 11, 2026

addedInput schema / properties / direction

Added value: +{
+  "description": "Deck-level writing direction, inherited by every slide (a slide-level direction wins) — set it once for an Arabic/Hebrew deck. Covers/dividers rendered on an UPLOADED brand template keep that template's own layout direction. See create_slide.direction.",
+  "enum": [
+    "ltr",
+    "rtl"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedAug 9, 2026

changedInput schema / properties / allow_partial / description

Previous value: -"Non-regret default: if any slide fails, the deck is NOT billed (cost:0) and pptx withheld — the response carries repair_actions (assemble the completed children, free). Set true to render + bill the completed slides and get the partial deck. Default false."New value: +"IGNORED. A deck bills per rendered slide and always returns its pptx; slides that failed or rendered badly are free and named in repair_actions."

changedInput schema / properties / force_render / description

Previous value: -"If any slide is completed_with_errors, deck pptx_url is null. Set true to get it anyway; complete slides stay downloadable via their per-slide job_id either way. No cost/status effect."New value: +"IGNORED (deck-level). pptx_url is always returned when at least one slide rendered, so there is nothing to force. Still meaningful on create_slide."

Changed2 schema fields changedAug 3, 2026

addedInput schema / properties / imagery

Added value: +{
+  "description": "Deck-level imagery mode, inherited by every slide (a slide-level imagery wins). See create_slide.imagery.",
+  "enum": [
+    "photo",
+    "wash",
+    "off"
+  ],
+  "type": "string"
+}

addedInput schema / properties / imagery_tag

Added value: +{
+  "description": "Deck-level subject declaration, inherited by every slide (a slide-level imagery_tag wins). Declare it once for a whole deck. See create_slide.imagery_tag.",
+  "enum": [
+    "general",
+    "agriculture",
+    "construction",
+    "education",
+    "energy",
+    "finance",
+    "government",
+    "healthcare",
+    "logistics",
+    "manufacturing",
+    "retail",
+    "technology",
+    "travel"
+  ],
+  "type": "string"
+}

Changed1 schema field changedJul 29, 2026

changedInput schema / properties / language / enum

Previous value: -[
-  "en",
-  "de",
-  "fr",
-  "es",
-  "it",
-  "pt",
-  "nl",
-  "pl"
-]New value: +[
+  "en",
+  "de",
+  "fr",
+  "es",
+  "it",
+  "pt",
+  "nl",
+  "pl",
+  "ru",
+  "uk"
+]

First observedJul 24, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations are sparse, but the description discloses substantial runtime behavior: parallel filling and merging into one themed PPTX, deck-level furniture, free vs paid modes, theme_id not re-theming assembled decks, dry_run returning a validation manifest, and force_render/allow_partial being ignored. It also explains billing ('bills per rendered slide') and repair_actions for failed slides, which annotations do not convey.

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 first sentence front-loads the core action and product, and the rest is dense but purposeful. The blocked-error handling, mode explanations, and polling note are compact yet scannable, with no filler or redundant restatement of the schema.

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?

Even with no output schema, the description covers return behavior enough for invocation: pptx_url is always returned when a slide rendered, dry_run returns a per-slide manifest, policy gates return rejected/cost:0, and polling uses deck_id == job_id via manage_account. Combined with the rich schema, it gives the agent what it needs to create, validate, assemble, fork, and troubleshoot a deck.

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 coverage is already high, but the description adds meaning not present in the schema: what mode values do, why dry_run belongs at deck level, how deck_id behaves for fork/update, the ignored force_render/allow_partial behavior, and how job_ids relate to assemble. It also points to create_slide for inherited slide-level parameter semantics, reducing ambiguity.

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?

Opens with a concrete verb and resource: 'Create a complete PowerPoint presentation (.pptx): a whole multi-slide deck, native and editable, in one call.' It explicitly frames slides as create_slide intents, so an agent can distinguish deck-level creation from the single-slide sibling and from modes like assemble/fork.

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?

The description tells when to use render vs assemble vs fork, tells the agent to see create_slide for slide-form details, routes blocked cases to browse_catalog(type=schema), and points to manage_account for job polling. It also instructs the agent to put dry_run at deck level rather than on individual slides, which is clear operational guidance.

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

All SlideForge tools Inspect

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.

Create Multi-Slide Deck

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources