Skip to main content
Glama

create_motion_scene

Validate and append a real shot to a new timeline file without overwriting existing work, enabling evidence-bound motion scenes for editable Remotion projects.

Instructions

Validate and append a real shot to a new timeline file; no destructive overwrite.

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>",
      "shot": "<shot>",
      "output": "<output>"
    },
    "name": "create_motion_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
shotYes
outputYes
timelineYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the "no destructive overwrite" claim is consistent but largely redundant. The description does add that validation occurs before the write, yet it never says what validation enforces, what happens if the timeline path exists, or whether a failed validation leaves partial output.

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?

A single front-loaded sentence with a semicolon-separated safety clause; there is no filler and the core action appears first.

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 is present, so return values need not be described, but a write tool operating on a deeply nested shot specification with zero schema coverage needs far more. Nothing explains validation rules, how the timeline and output paths relate, or what a caller must supply in the shot object, which is inadequate for this complexity.

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

Parameters2/5

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

Schema description coverage is 0% and the schema contains a nested shot object with ten properties including enums, duration bounds, and a required evidence field. The description contributes only the loose notion that a "shot" is appended to a "timeline" file, leaving the meaning of output, the relationship between timeline and output, and the evidence requirement entirely undocumented.

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 uses a concrete verb pair ("validate and append") and identifies both the resource (a shot) and the target (a new timeline file), which is clear enough to act on. It stops short of distinguishing itself from siblings such as create_scene_plan or generate_3d_scene, so the agent must infer the boundary.

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?

"New timeline file" implies the tool is for starting a fresh timeline rather than adding to an existing one, and "no destructive overwrite" hints at a safety scope. There is no explicit when-to-use guidance, no statement of prerequisites, and no direction to alternatives for existing timelines.

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