Skip to main content
Glama

Export Deck Slides (permanent files)

antix_export_deck
Idempotent

Export a carousel deck's slides as PERMANENT, full-resolution image files and return their direct URLs. FREE, rate-limited. Use this whenever the files leave AIGE — a scheduler (Buffer), an uploader, or the user downloading them.

Do NOT hand out antix_get_deck's previewUrl for that: previews are 540px WebP approximations under the daily scheduled preview cleanup (14 days), which also prunes to the three newest design versions. These export URLs are public, full-resolution and never reaped.

A browser-finalized export always wins and is returned as-is (exportSource: "browser"); every other slide is rendered server-side once at full resolution and REUSED on later calls for the same designVersion and format — calling twice re-renders nothing. bufferAssets mirrors slides in Buffer's own create_post asset shape: { image: { url, metadata: { altText } } }.

If you just called antix_generate_deck_slide_images, wait for antix_check_deck_readiness to report no missing_photo before exporting — the response's pendingArt flag tells you when slides were exported without their art.

Instagram autopublish is NOT available — exporting hands YOU the files; it posts nothing anywhere. To post to a connected Instagram/Threads channel instead, use antix_compose_social_post.

Input Schema

NameRequiredDescriptionDefault
deckIdYesDeck to export. Get ids from antix_get_deck.
formatNoOutput file format. Default png.
slideIdsNoExport only these page ids. Omit to export every slide in deck order.
knownDesignVersionNoThe designVersion you already have; the response reports upToDate. Exports always target the deck's CURRENT version.

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?

Beyond the annotations, it discloses that exports are permanent, public, full-resolution, and never reaped, unlike previews subject to 14-day cleanup and pruning. It explains browser-finalized export precedence, server-side rendering reuse per designVersion/format, and the pendingArt flag when art is missing.

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 main purpose and key warning are front-loaded, and the remaining paragraphs are organized around alternatives, caching behavior, response shape, and caveats. It is somewhat dense and long, but nearly every sentence provides actionable information rather than restating structured fields.

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 no output schema, the description explains the returned URLs, exportSource semantics, bufferAssets shape, and pendingArt signal. It also covers the main operational caveat that Instagram autopublish is unavailable and points to the alternative tool.

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 deckId, format, slideIds, and knownDesignVersion. The description still adds behavioral meaning by explaining that exports always target the current version and that rendering is reused across calls for the same designVersion and format.

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?

The description states a specific verb and resource: export a carousel deck's slides as permanent, full-resolution image files with direct URLs. It explicitly distinguishes itself from antix_get_deck's previewUrl and from antix_compose_social_post, so an agent can identify the correct tool without inspecting schemas.

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?

It names concrete use cases (scheduler, uploader, user download) and explicitly says not to hand out previewUrl for those cases. It also gives sequencing guidance with antix_check_deck_readiness and redirects posting use cases to antix_compose_social_post.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources