Skip to main content
Glama

Create slideshow run

create_slideshow_run

Creates a durable multi-page social slideshow run from a structured ContentPack, applying brand settings and returning an authoring URL for review and PNG download.

Instructions

Create a durable multi-page Slideshow Run from a structured ContentPack (platform + pages; each page carries role, slots and either a generated layout { studioJson, canvas } adapted from a Deck Style family, or a layoutFamilyId). Pass brandId to apply the user Brand. Put the post text beside the images in pack.post { title?, description? } (Xiaohongshu / TikTok have a title; Instagram, Threads, LinkedIn and X use description). X image Runs support 2–20 pages and default to the Instagram-compatible 4:5 canvas. Do NOT use to edit an existing run (use update_slideshow_run instead). Requires workspace owner write authorization. Returns created SlideshowRun record with generated runId, initial revision (1), and authoringStudioUrl for interactive browser review and PNG download.

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": {
      "pack": "<pack>"
    },
    "name": "create_slideshow_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
packYescontent-pack.v1 payload containing schemaVersion, platform, and pages array with bound templateId and slots content.
brandIdNoOptional Brand ID to apply brand kit typography, colors, and logo to all slides.
contentSlugNoOptional content topic identifier for tracking in Content Engine.
brandProfileIdNoOptional legacy brand profile ID.

Output Schema

NameRequiredDescriptionDefault
runIdNoUnique identifier of the created run.
revisionNoInitial revision number (1).
studioUrlNoStudio preview and download URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.17
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "revision": {
      +      "description": "Initial revision number (1).",
      +      "type": "number"
      +    },
      +    "runId": {
      +      "description": "Unique identifier of the created run.",
      +      "type": "string"
      +    },
      +    "studioUrl": {
      +      "description": "Studio preview and download URL.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed4 schema fields changedv0.1.16
    • addedInput schema / properties / brandId / description
      Added value: +"Optional Brand ID to apply brand kit typography, colors, and logo to all slides."
    • addedInput schema / properties / brandProfileId / description
      Added value: +"Optional legacy brand profile ID."
    • addedInput schema / properties / contentSlug / description
      Added value: +"Optional content topic identifier for tracking in Content Engine."
    • addedInput schema / properties / pack / description
      Added value: +"content-pack.v1 payload containing schemaVersion, platform, and pages array with bound templateId and slots content."
  3. First observedv0.1.13

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare the safety profile (non-read-only, non-destructive, non-idempotent, closed-world); the description adds authorization requirements, platform-specific page limits (X supports 2-20 pages), the default 4:5 canvas, and the concrete return contents including runId, initial revision 1, and authoringStudioUrl. That is substantial context beyond the annotations, though it does not discuss failure modes or rate/durability limits on generation.

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 definition is dense but front-loaded: purpose first, then pack structure, then the exclusion, then authorization, then return value. Every sentence carries information, though the single unbroken paragraph makes the several distinct concerns harder to scan than a short bulleted structure would.

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 creation tool with nested objects and an output schema, this covers what the schema cannot: authorization, platform-specific constraints, default canvas, and where post text lives. Return values are summarized even though an output schema exists, leaving no significant gap for correct invocation.

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 baseline would be 3, but the description goes further by explaining the pack's internal structure (platform, pages, per-page role/slots, layout vs layoutFamilyId, and pack.post title/description with platform-specific naming). It does not clarify brandProfileId or contentSlug, which the schema handles instead.

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 names a specific verb and resource (create a durable multi-page Slideshow Run) and immediately specifies the input shape (a structured ContentPack with platform and pages). It explicitly separates itself from update_slideshow_run, so an agent can distinguish it from the closest sibling 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?

It gives an explicit negative case ("Do NOT use to edit an existing run (use update_slideshow_run instead)") and names the alternative. It also states the prerequisite (workspace owner write authorization) and when to supply brandId, which is exactly the routing information an agent needs.

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