Reel-E

Use an AI+ version

use_ai_version

Destructive

Switches an AI+ shot to one of its saved versions (a number from list_ai_versions). Uses no credit; undoable. A version made for a shorter spot can't fill a longer shot; a shot without AI+ gets it with request_ai_plus, which reuses a matching saved version without a new credit.

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>",
      "photoId": "<photoId>",
      "version": "<version>"
    },
    "name": "use_ai_version"
  }
}

Input Schema

Name	Required	Description
`photoId`	Yes	A photo: its photoId from the edit summary, or its play position like "shot 3".
`version`	Yes	The saved AI+ version to use: its number from list_ai_versions.
`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 / version / description
```
Added value: +"The saved AI+ version to use: its number from list_ai_versions."
```
First observedNov 9, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds real context beyond that by disclosing the cost model ('uses no credit') and reversibility ('undoable'), which materially change an agent's willingness to call it. What it does not spell out is what the previously selected version becomes after the switch, which is the exact thing the destructive hint flags.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action, then cost, then constraints and alternatives. Every clause carries information an agent needs; there is no restating of the title or the parameter list.

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?

The tool mutates state but annotations cover the safety profile, the input schema is fully documented, and an output schema exists, so the description only needs to contribute cost, reversibility, and compatibility rules — which it does. Nothing an agent needs in order to call it correctly against the routing siblings is missing.

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, and the description adds meaning on top: the 'version' value is a number obtained from list_ai_versions, and the length-compatibility constraint qualifies which version numbers are even legal for a given shot. That constraint is a semantic rule absent from the schema's minimum:1 integer definition.

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: 'Switches an AI+ shot to one of its saved versions.' It immediately distinguishes itself from the sibling that produces those versions ('a number from list_ai_versions') and from the sibling that adds AI+ ('request_ai_plus'), so an agent can tell which operation it is without reading schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing in both directions: use this when a shot already has AI+ and you want a different saved version, and use request_ai_plus instead when the shot has no AI+ at all. It also states the blocking condition ('a version made for a shorter spot can't fill a longer shot'), which prevents a foreseeable failed call.

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?