Reel-E

Edit style

set_edit_style

Destructive

The video's edit style, the same switch as the Music panel's: cinematic (the default, today's edit), flow (Flow: a push and an orbit each bar to the drop, then Boomerangs on the beat; AI+ is off in Flow and its clips come back in cinematic) or fast_cuts (Fast Cuts: a cut on every beat after the drop). Available when the edit summary has an EDIT STYLE line. A style writes each shot's length, Movement and transition (editable after) and sets the song start so the drop lands on a cut; Fast Cuts sets AI Seamless aside, Flow sets AI+ aside and the AI Seamless pairs that touch its Boomerangs or ramps. Uses no credit; undoable.

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>",
      "style": "<style>"
    },
    "name": "set_edit_style"
  }
}

Input Schema

Name	Required	Description	Default
`style`	Yes	The edit style: cinematic (default), flow or fast_cuts.
`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 / style / description
```
Added value: +"The edit style: cinematic (default), flow or fast_cuts."
```
First observedNov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by specifying exactly what is overwritten (each shot's length, Movement and transition), what is disabled per style (AI+ in Flow, AI Seamless in Fast Cuts and the pairs touching its Boomerangs/ramps), and that the song start is shifted so the drop lands on a cut. It also closes the two questions an agent always has for a destructive mutation: 'Uses no credit; undoable.'

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?

Information density is high and almost nothing is filler, but it is delivered as one sprawling sentence with deeply nested parentheses, which makes it hard to scan. The 'same switch as the Music panel's' framing is UI-oriented and adds little for an agent; a bulleted per-style breakdown would have been clearer at the same length.

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 only two fully documented parameters and an existing output schema, the description covers everything that matters: availability condition, side effects on other settings, credit cost and undo support. An agent can call it correctly and predict its consequences without opening other tools.

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 baseline is 3, but the description genuinely enriches the enum: cinematic is the default ('today's edit'), Flow animates a push and orbit per bar then Boomerangs on the beat, Fast Cuts cuts on every beat after the drop. listingId is left to the schema's own pointer to list_listings, which is adequate.

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?

Names a specific setting (the video's edit style) and enumerates all three values with a one-line characterization of each. It also implicitly distinguishes itself from the granular setters by stating 'A style writes each shot's length, Movement and transition (editable after)', so an agent can tell this preset switch apart from set_shot_length/set_movement/set_transition.

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?

Gives a concrete precondition – 'Available when the edit summary has an EDIT STYLE line' – which tells the agent when the call is legal. It also signals that this tool overrides per-shot settings that remain editable afterwards, but it never names a sibling tool to use instead when the user only wants to tweak one attribute.

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?