Skip to main content
Glama

Prepare connected video shots from a text group

playground_storyboard_prepare
Idempotent

Create ready-to-generate video shot nodes connected to text nodes inside a selected text group. This only prepares nodes; it does not submit paid video jobs. Requires the latest canvas revision. Returns shot node IDs, source node ID, optional stitch/group IDs and revision.

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>",
      "sourceNodeId": "<sourceNodeId>",
      "modelId": "<modelId>",
      "aspectRatio": "<aspectRatio>",
      "shots": "<shots>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "playground_storyboard_prepare"
  }
}

Input Schema

NameRequiredDescriptionDefault
shotsYes
modelIdYesCanonical model ID returned by model discovery or resolution; preserve the user’s selected model.
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
aspectRatioYesOutput width-to-height ratio supported by the selected model, such as 1:1 or 9:16.
sourceNodeIdYesExisting canvas source node ID to use for this operation.
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
groupIdNo
replayedYes
revisionYes
shotNodeIdsYes
sourceNodeIdYes
stitchNodeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, but the description adds materially useful context beyond them: it creates nodes without submitting paid jobs, and it demands the latest canvas revision. That cost-safety distinction is exactly the kind of thing an agent needs before calling a mutating tool. It stops short of describing failure modes (revision_conflict handling lives only in the schema).

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?

Three sentences, each carrying a distinct payload: what it creates, what it deliberately does not do, and what it requires and returns. The cost guard is front-loaded in sentence two where an agent will see it before deciding to call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-required-parameter mutation with an output schema present, the definition covers the essentials: naming the precondition (fresh revision) and the no-paid-jobs boundary. Listing return fields duplicates the output schema slightly, and nothing explains what happens if a sourceTextNodeId is not inside the selected group, but overall an agent has enough to call it correctly.

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 description coverage is 86%, so the schema already documents nearly every parameter, including idempotencyKey and expectedRevision semantics. The description adds only light framing: that shots bind to 'text nodes inside a selected text group,' which clarifies sourceTextNodeId/sourceNodeId intent. With the schema doing the heavy lifting, baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Create ready-to-generate video shot nodes connected to text nodes inside a selected text group.' That is far more precise than the title alone, and the clause 'does not submit paid video jobs' separates it from the generation/confirmation tools in the sibling list. It never names a sibling alternative by name, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer 'use this to turn a text group into connected shot nodes before generating.' The 'Requires the latest canvas revision' line is a real precondition that steers the agent to canvas_read first. However, there is no explicit when-not guidance (e.g., when to prefer playground_content_prepare or canvas_add_text instead).

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.