Skip to main content
Glama

Attach a clip to a scene

set_scene_clip
Destructive

Attach existing footage to one scene: an owned ready clip generation, a verified video upload, or a finished storyboard render. Replaces the scene's clip and keeps its still; nothing is generated. One undo step; undo_storyboard takes it back. Spends no credits.

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": {
      "storyboard_id": "<storyboard_id>",
      "scene": "<scene>",
      "reference": "<reference>"
    },
    "name": "set_scene_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneYes
referenceYesAn owned ready clip generation, verified video upload, or finished storyboard render. Attaches existing footage without generating anything; the scene keeps its still.
storyboard_idYes

Output Schema

NameRequiredDescriptionDefault
castYes
briefYes
notesYes
quoteNo
textsYes
scenesYes
soundsYes
videosYes
creditsYes
historyYes
messageYes
skippedNo
startedNo
stoppedNo
acceptedNo
receiptsNo
scheduleYes
settingsYes
referenceNo
storyboardYes
download_urlNo
generation_idNo
remaining_scenesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description adds important behavioral details: it replaces the scene's existing clip, preserves its still, generates nothing, costs no credits, and is reversible via undo_storyboard. These details materially inform an agent about side effects and safety.

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?

The description is three tightly written sentences with no wasted words. The key behavior and cost/undo context are front-loaded.

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 the output schema, annotations, and the tool's moderate complexity, the description provides enough context for correct invocation: source types, replacement behavior, undo path, and no-credit cost are all covered.

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 only 33%, so the description must compensate. It does explain the reference variants well, but it does not clarify storyboard_id or scene semantics beyond the schema's basic types and minimum constraint.

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 description states a specific verb and resource: attach existing footage to one scene. It also enumerates the three acceptable source types and contrasts with generation by saying 'nothing is generated,' which helps distinguish it from sibling generation tools.

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?

The description clearly establishes when to use the tool: when attaching already-existing footage rather than generating it. It also names undo_storyboard as the reversal path. It does not explicitly compare against siblings like generate_clip or set_scene_image, so it stops short of a full when-to-use/when-not-to-use guide.

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