Reel-E

Transition

set_transition

Destructive

The transition after a shot: cut, speed_ramp or dissolve. Not available before the last shot or next to an AI+ shot. After the first shot it is available only while the opening title is off (the title plays over that whole shot); with the title on, it comes back as a choice for the person.

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>",
      "afterPhotoId": "<afterPhotoId>",
      "transition": "<transition>"
    },
    "name": "set_transition"
  }
}

Input Schema

Name	Required	Description
`listingId`	Yes	Listing id from list_listings.
`transition`	Yes	The transition after the shot: cut, speed_ramp or dissolve.
`afterPhotoId`	Yes	A photo: its photoId from the edit summary, or its play position like "shot 3".

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 / transition / description
```
Added value: +"The transition after the shot: cut, speed_ramp or dissolve."
```
First observedNov 9, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already declare a destructive, non-idempotent mutation, and the description adds useful availability constraints beyond that. However, it does not state what happens to an existing transition or clarify the practical destructive/non-idempotent effects.

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 description is front-loaded with the core purpose and then gives availability rules in two compact sentences. A few phrases, especially 'comes back as a choice for the person,' are slightly opaque but not wasteful.

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?

Given the full parameter coverage, output schema, and annotations, the description supplies the key conditional availability information an agent needs before calling. It still leaves overwrite behavior implicit, but the destructive annotation provides a safety warning.

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 parameters are already well documented. The description repeats the transition enum and after-shot context but adds no additional parameter syntax, format, or edge-case meaning.

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 states the resource and exact enum choices: the transition after a shot, with cut, speed_ramp, or dissolve. It is clear what the tool modifies, but it does not explicitly distinguish itself from sibling tools such as set_fades or set_movement.

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 gives explicit availability and exclusion rules: not before the last shot, not next to an AI+ shot, and first-shot behavior depending on whether the opening title is on. It does not name alternative tools for cases where this transition is unavailable.

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?