Reel-E

Pace

set_pace

Destructive

Makes the edit faster paced, slower and more cinematic, or back to normal, as one undoable change. By default (amount a_little) every other shot takes a half-length or double-length beat-aligned step; amount a_lot steps every shot, for much faster or much slower. A shot whose length or speed was already chosen keeps it unless named. The first and last shots and AI+ shots keep their fixed length. The video stays on the song's beat grid; read_music_structure shows where the cuts now land.

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>",
      "pace": "<pace>"
    },
    "name": "set_pace"
  }
}

Input Schema

Name	Required	Description
`pace`	Yes	faster, slower (more cinematic) or normal.
`amount`	No	Default a_little. a_lot only for 'much faster' or 'much slower'.
`photoIds`	No	Optional: only these shots. Default: every shot.
`listingId`	Yes	Listing id from list_listings.

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026
- addedInput schema / properties / pace / description
```
Added value: +"faster, slower (more cinematic) or normal."
```
First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the destructiveHint/readOnlyHint annotations, it discloses that the change is undoable, exactly which shots are stepped at each amount, that first/last and AI+ shots keep fixed length, and that pre-set shot lengths are not overridden unless named. That is rich, non-obvious behavior for a mutation tool.

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?

The core action is front-loaded, followed by defaults, exceptions, and a follow-up pointer, with no filler. It is denser than typical and the final sentence is a nice-to-have rather than essential, but nothing is redundant.

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?

For a destructive, non-idempotent mutation with an output schema, the description covers defaults, exceptions, reversibility, and the natural follow-up check. An agent has everything needed to call it correctly without reading other docs.

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

Parameters4/5

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

Schema coverage is 100%, so the parameters are already documented; the description still adds meaning by specifying the default amount behavior and the 'unless named' override rule that governs photoIds targeting. Slightly above the baseline because it explains interaction, not just naming.

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 gives a specific verb and resource: it retimes the edit's shots to be faster, slower/cinematic, or normal, as a single undoable change. It also implicitly separates itself from the per-shot length/speed tools by noting that a shot whose length or speed was already chosen is preserved, so an agent can tell which knob this turns.

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?

It clearly frames the three modes and the amount default (a_little for the ordinary case, a_lot only for 'much faster' or 'much slower'), and points to read_music_structure to see where cuts now land. It stops short of explicit when-not-to-use guidance against siblings like set_shot_length or set_shot_speed, leaving that to inference.

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?