easysociable-mcp

Create slideshow run

create_slideshow_run

Create a durable multi-page slideshow run from a structured ContentPack with platform, bound template IDs, and slot text. Select templates first; it returns a run ID and authoring URL.

Instructions

Create a durable multi-page Slideshow Run from a structured ContentPack (specifying platform, pages array with bound templateId and slot text values). Call recommend_slideshow_templates first to select templates. 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.

Input Schema

TableJSON Schema

Name	Required	Description
`pack`	Yes	content-pack.v1 payload containing schemaVersion, platform, and pages array with bound templateId and slots content.
`brandId`	No	Optional Brand ID to apply brand kit typography, colors, and logo to all slides.
`contentSlug`	No	Optional content topic identifier for tracking in Content Engine.
`brandProfileId`	No	Optional legacy brand profile ID.

Output Schema

TableJSON Schema

Name	Required	Description
`runId`	No	Unique identifier of the created run.
`revision`	No	Initial revision number (1).
`studioUrl`	No	Studio preview and download URL.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.17Oct 5, 2026

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"
+}

Changed4 schema fields changedv0.1.16Oct 5, 2026

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."

First observedv0.1.13Oct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, and destructive=false, so the write/safety profile is covered. The description adds real value beyond that: it flags the durable nature, states the 'workspace owner write authorization' requirement, and describes the returned artifacts. It stops short of noting rate limits or failure modes, so it lands at 4 rather than 5.

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?

Front-loaded with the core action and input, followed by prerequisite, exclusion, auth, and return value in a compact block. Every clause earns its place, though the return-value sentence is slightly redundant given an output schema exists.

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 mutation tool with a nested ContentPack input, the definition covers purpose, prerequisite, exclusion, authorization, and the resulting record. Since an output schema exists, the return description is a bonus rather than a gap, leaving nothing an agent needs missing.

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

Parameters3/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 all four parameters, establishing a baseline of 3. The description reinforces the structure of the required 'pack' (platform, pages array with bound templateId and slot text values) but adds little beyond the schema and never mentions the optional brandId/contentSlug/brandProfileId parameters.

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 ('Create a durable multi-page Slideshow Run from a structured ContentPack') and clarifies the input contract. It explicitly distinguishes itself from update_slideshow_run, so an agent can tell the two apart without opening 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?

Gives an explicit prerequisite ('Call recommend_slideshow_templates first') and an explicit exclusion ('Do NOT use to edit an existing run (use update_slideshow_run instead)'). The alternative is named with the condition that selects it.

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