Skip to main content
Glama

Assemble Playground clips into one film

playground_media_compose
Idempotent

Stitch 2–12 finished video nodes, in the given order, into one film. Creates an "Assemble film" (video-stitch) node wired from the clips and queues the existing FFmpeg film worker, which normalizes the clips, concatenates them and attaches the MP4 to that node. Clips must be generated video nodes in this project's storage sharing one 16:9, 9:16 or 1:1 aspect ratio. Free: no credits are spent. Returns immediately; poll playground_run_delivery with the returned runId (every ≥30 s) until verified, or read the stitch node's generated URL with playground_node_get.

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": {
      "projectId": "<projectId>",
      "expectedRevision": "<expectedRevision>",
      "idempotencyKey": "<idempotencyKey>",
      "videoNodeIds": "<videoNodeIds>"
    },
    "name": "playground_media_compose"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoHuman-readable label to display for this item in Playground.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
videoNodeIdsYesSource video node IDs in the order they should appear in the assembled video.
idempotencyKeyYesUnique key for this request; reuse only when retrying the identical request after a lost response. Use a new key after quoting or changing inputs.
expectedRevisionYesCurrent canvas revision from canvas_read; on revision_conflict, read again and rebuild the change.

Output Schema

NameRequiredDescriptionDefault
pollYes
errorNo
runIdYes
statusYes
replayedYes
revisionYes
canvasUrlYes
onFailureYes
shotNodeIdsYes
stitchNodeIdYes
conversationIdYes
retry_after_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds substantial information beyond them: the tool is asynchronous and returns immediately, it is free (no credits), it creates and wires a downstream node, the worker normalizes and concatenates clips, and polling should be at intervals of at least 30 seconds. That is exactly the operational context an agent needs to avoid re-calling or mis-polling.

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?

Four sentences, front-loaded with the action and the count/order constraint, followed by side effects, preconditions and the follow-up path. No filler, and the free/async facts appear before the polling instructions.

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?

Given an output schema exists, the description needn't explain return values, yet it still names runId and the two ways to confirm completion, which closes the async loop for the caller. For a multi-step, non-destructive mutation with preconditions, nothing essential is 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 all five parameters already carry their own descriptions, establishing a baseline of 3. The description reinforces that clip order matters and that 2–12 clips are produced, but that ordering semantics is already stated in the videoNodeIds schema text, so little new meaning is added.

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 — 'Stitch 2–12 finished video nodes, in the given order, into one film' — plus the concrete side effects (creates an Assemble film node, queues the FFmpeg worker). This is clearly distinguishable from generation tools like playground_media_generate and from read tools like playground_node_get.

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

Usage Guidelines4/5

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

Gives real preconditions (clips must be generated video nodes in this project's storage sharing one 16:9/9:16/1:1 aspect) and explicitly routes the agent to playground_run_delivery for polling and playground_node_get for the result. It lacks an explicit 'do not use this when…' exclusion, so it is a 4 rather than a 5.

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.