Skip to main content
Glama

generate_storyboard

Validate evidence-bound shots from supplied product claims and screenshots, then persist a renderable timeline for building promotional videos.

Instructions

Validate evidence-bound shots and persist a real renderable timeline. Client supplies product claims and screenshots.

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

Input Schema

NameRequiredDescriptionDefault
outputYes
timelineYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description's marginal job is to explain what actually gets written and what validation failure looks like. It only gestures at this with 'persist a real renderable timeline' — it does not say whether a file is created at the `output` path, whether existing files are overwritten (important given idempotentHint=false), or what happens when evidence checks fail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler, and the action is front-loaded. However, the second sentence ('Client supplies product claims and screenshots') is a vague restatement of inputs that spends a sentence without telling the agent which fields carry those values.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but the tool's real complexity is in the input: a nested shot array with five enums and per-shot evidence constraints, none of which the description addresses. For a mutation tool that writes a renderable artifact, the definition leaves the agent without enough to construct a valid call or predict side effects.

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

Parameters1/5

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

Schema description coverage is 0% and the schema is deeply nested (timeline.shots[] with evidence, asset, kind, motion, duration, transition, plus fps/crf/direction/encodingPreset), so the description must compensate — and it does not. Neither top-level parameter is explained: `output` is never mentioned and `timeline` is only alluded to as 'product claims and screenshots', which maps to no actual field name. The 'evidence-bound' phrase is the only semantic hint, and it is unexplained.

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

Purpose3/5

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

States specific verbs ('validate', 'persist') and a resource ('renderable timeline', 'evidence-bound shots'), but never plainly says it produces a storyboard, which the tool name implies, and the relationship between 'validate' and 'persist' is left ambiguous. No sibling is referenced, so the agent cannot tell from the text how this differs from generate_remotion_project or create_scene_plan.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no exclusions. The agent is not told whether a brief or scene plan must exist first, nor when to prefer this over the other generate_* tools in the catalog.

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