Reel-E

Camera movement

set_movement

Destructive

Standard camera movement for shots. An AI+ shot plays one gentle push-in and has no move to choose, so it is skipped; if every named shot is AI+ the tool refuses. It does not remove AI+ from a shot.

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": {
      "listingId": "<listingId>",
      "photoIds": "<photoIds>",
      "movement": "<movement>"
    },
    "name": "set_movement"
  }
}

Input Schema

Name	Required	Description
`movement`	Yes	The camera move: push-in, pull-out, orbit-right or orbit-left.
`photoIds`	Yes	The shots: each a photoId from the edit summary, or a play position like 'shot 3'.
`listingId`	Yes	Listing id from list_listings.

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

addedInput schema / properties / movement / description

Added value: +"The camera move: push-in, pull-out, orbit-right or orbit-left."

addedInput schema / properties / photoIds / description

Added value: +"The shots: each a photoId from the edit summary, or a play position like 'shot 3'."

First observedNov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already flag this as a destructive, non-idempotent write, and the description adds genuinely new behavior: per-shot skipping and an all-AI+ refusal. It does not say whether an existing movement on a targeted shot is overwritten or what the refusal response looks like, which is the remaining gap for a destructive mutation.

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?

Three dense sentences with the default behavior front-loaded ahead of the edge cases; nothing is filler. The phrasing 'has no move to choose' is slightly telegraphic but the sequence is logical.

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

Completeness4/5

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

For a destructive, non-idempotent three-parameter mutation with a full schema and an output schema, the description covers the unusual failure modes well. Overwrite semantics for already-set movement are the one omission, which is minor given the schema does the parameter work.

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 coverage is 100% and the movement enum is fully self-documenting, so the baseline is 3. The description adds the useful semantic that photoIds containing AI+ shots are skipped rather than erroring, but says nothing about the listingId or about whether photoIds means whole shots or frames.

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 names the resource (camera movement applied to shots) and its scope, and distinguishes this from what the tool is not (it does not remove AI+ from a shot). It never states the verb explicitly, relying on the name and title to supply 'set', so an agent infers the operation rather than reading it.

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

Usage Guidelines3/5

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

The exclusions are stated precisely: AI+ shots are skipped, and the call is refused if every named shot is AI+. No alternative is named for unsetting a move or for handling AI+ shots, so an agent knows the boundaries but not where to redirect.

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

All Reel-E tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?