Skip to main content
Glama

Generate storyboard

generate_storyboard
Destructive

Plans the scenes from the script, actor and product photos. Runs in the background for 1–3 minutes: poll get_project until storyboard.scenes > 0, then review the scenes with the user. Needs a paid plan. Regenerating replaces the scenes. video_quality picks the models the video is filmed with: "standard" (default — Grok Imagine and MiniMax H3, affordable) or "premium" (Seedance 2.5 for every scene, most realistic, about 29 credits per second of video; English only for now). Ask the user which they want before the first storyboard.

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": {
      "project_id": "<project_id>"
    },
    "name": "generate_storyboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesThe project's id.
video_qualityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description earns credit by explaining exactly what is destroyed ('Regenerating replaces the scenes') plus the long-running async behavior (1–3 minutes in background) and paid-plan gating. Cost and language limits for the premium tier are disclosed, which is context annotations cannot carry.

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?

Purpose is front-loaded in sentence one, and every sentence carries operational value — none is filler. The video_quality sentence is a long nested parenthetical that is dense on first read, but the detail is genuinely decision-relevant rather than padding.

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 an async, costly, destructive generation tool with no output schema, the description covers the full lifecycle: trigger, wait duration, completion signal via get_project, user review, and regeneration semantics. Nothing an agent needs to call this correctly or recover from it is missing.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% and video_quality has no schema description, but the description fully compensates: it explains that it selects the underlying video models, gives the default ('standard'), names the models in each tier, and quantifies the premium cost (~29 credits/second) with an English-only caveat. project_id is covered by the schema.

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 first sentence names a specific verb+resource ('Plans the scenes') and states the inputs it consumes (script, actor and product photos), which distinguishes it from generate_script and start_video_generation among the siblings. An agent can tell what it produces without opening the 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 prerequisite ('Needs a paid plan'), an explicit polling loop ('poll get_project until storyboard.scenes > 0'), a sequencing instruction (review with the user, ask about quality before the first storyboard), and a warning that regenerating replaces existing scenes. That is when-to-use, ordering, and an alternative data source all in one.

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