Reel-E

Shot speed

set_shot_speed

Destructive

Playback speed of the camera movement: slow (0.5x), normal or fast (2x).

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>",
      "speed": "<speed>"
    },
    "name": "set_shot_speed"
  }
}

Input Schema

Name	Required	Description
`speed`	Yes	Camera movement speed: slow (0.5x), normal or fast (2x).
`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 / photoIds / description

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

addedInput schema / properties / speed / description

Added value: +"Camera movement speed: slow (0.5x), normal or fast (2x)."

First observedNov 9, 2026

TDQS

C2.5/5.0

Behavior2/5

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

Annotations declare this is a non-idempotent, destructive write, so the safety profile is covered — but the description adds nothing on top: it does not say existing speed settings are overwritten, that it applies only to the listed photoIds, or that the listing must already exist. For a destructive mutation, silence on what gets replaced is a real gap.

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?

It is a single short fragment with no wasted words and the key attribute is front-loaded. But the terseness comes at the cost of under-specification rather than efficiency — one more clause on scope or effect would earn its place.

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 explained, but for a three-required-parameter destructive mutation the description omits which shots are affected, whether prior speed is replaced, and any permission or workflow prerequisites. It is too thin for the tool's complexity.

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 100%, so the baseline is 3. The description's value mapping (slow 0.5x, fast 2x) is verbatim identical to the enum description already in the schema, so it contributes no meaning beyond the structured fields.

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?

The description names the specific attribute being altered — the camera movement playback speed — and the tool name supplies the 'set' verb. However, the description itself is a bare noun phrase with no verb or object scope (which shots it applies to), so the purpose is only implied rather than stated. It is distinguishable from set_pace and set_movement only by inference from the words 'camera movement'.

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 guidance on when to use this tool, no prerequisites, and no mention of how it differs from nearby siblings such as set_pace, set_movement, or set_shot_length. The agent must infer that this controls per-shot camera speed rather than overall edit pacing entirely from the tool name.

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?