Reel-E

Fades

set_fades

Destructive

Turns the video's fades on or off: videoIn (fade in from black at the start), videoOut (fade out to black at the end), musicIn and musicOut (the music's fade in and out). Off leaves the video's length unchanged: the last frame or end card holds instead of going to black, and the music stops with the picture. Only the fades passed are changed. 'No fade at the end' means videoOut false (and musicOut false if the sound is meant too).

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

Input Schema

Name	Required	Description
`musicIn`	No	Fade the music in at the start.
`videoIn`	No	Fade in from black at the start.
`musicOut`	No	Fade the music out at the end.
`videoOut`	No	Fade out to black at the end.
`listingId`	Yes	Listing id from list_listings.

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 10, 2026
- addedInput schema / properties / musicIn / description
```
Added value: +"Fade the music in at the start."
```
- addedInput schema / properties / musicOut / description
```
Added value: +"Fade the music out at the end."
```
- addedInput schema / properties / videoIn / description
```
Added value: +"Fade in from black at the start."
```
- addedInput schema / properties / videoOut / description
```
Added value: +"Fade out to black at the end."
```
First observedNov 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Goes beyond the annotations by describing the visual consequence of turning fades off: the last frame or end card holds and total length is unchanged, and the music stops with the picture. That is real behavioral context an agent cannot get from the schema. It does not explain why the tool is flagged destructiveHint=true (e.g. whether existing rendered content is affected), which is the one unresolved gap.

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?

Front-loaded with the action, then the fade fields, then the off-behavior, then the partial-update rule. Dense and largely waste-free, though the closing quoted-phrase sentence reads as a scenario aside rather than core specification.

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?

With an output schema present, the return value need not be described, and all four fade parameters plus the partial-update rule are covered. What remains thin is guidance on when to reach for this versus set_music or set_transition, and what 'destructive' means in practice for this operation.

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 adds meaning beyond the one-line schema descriptions: it clarifies the boolean false case for each fade and that unpassed fades are left untouched. The listingId parameter is left to the schema, which is fine.

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?

States a specific verb and resource ('Turns the video's fades on or off') and then enumerates exactly which fades: videoIn, videoOut, musicIn, musicOut, each with a parenthetical definition. An agent can tell this apart from set_music or set_transition without opening the schema.

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?

Explains partial-update semantics ('Only the fades passed are changed') and translates a common user phrasing ('No fade at the end') into the concrete flags to send, including the nuance about musicOut. It gives no explicit comparison to sibling tools such as set_music, but the usage context is clear enough to act on.

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?