Skip to main content
Glama

create_camera_movement

Apply deterministic camera motion to an existing timeline shot, choosing push, pan, reveal, or hold and outputting the updated scene.

Instructions

Apply deterministic camera motion to an existing scene.

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>",
      "shotIndex": "<shotIndex>",
      "output": "<output>"
    },
    "name": "create_camera_movement"
  }
}

Input Schema

NameRequiredDescriptionDefault
motionNopush
outputYes
timelineYes
shotIndexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the bar is lower. 'Deterministic' adds a genuine behavioral claim beyond those annotations, but the description never says whether existing motion is overwritten, whether the operation is reversible, or why idempotentHint is false for a 'deterministic' operation — a tension an agent should be told about explicitly.

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?

A single front-loaded sentence with no filler or repetition. It is tight, though the brevity here reflects under-specification rather than economy.

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?

A mutation tool with 4 parameters at 0% schema coverage needs the description to carry parameter and side-effect detail, and it does not. An output schema exists so return values need not be explained, but the missing guidance on shotIndex/timeline semantics and overwrite behavior leaves it materially incomplete.

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% across 4 parameters, so the description must compensate and it says nothing about any of them. 'timeline', 'shotIndex' (a 0-29 bounded index), 'output', and the push/pan/reveal/hold motion enum receive no meaning beyond their bare names, leaving the agent to guess indexing base and expected values.

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 gives a specific verb and resource ('Apply deterministic camera motion to an existing scene'), which tells an agent the operation targets camera movement on an already-existing scene rather than creating one. It does not differentiate from look-alike siblings such as create_motion_scene, so it stops short of a 5.

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 statement of when to use this tool, when not to, prerequisites (does the scene need to already contain a shot at shotIndex?), or which sibling to prefer for adjacent motion work. The agent must infer placement from the name alone.

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