Reel-E

AI+ motion

request_ai_plus

Destructive

Generates cinematic AI motion for one shot (moving water, fire, people, trees). The camera on an AI+ shot is one gentle push-in, so there is no camera move to pick or describe; the prompt names what should move in the scene. Uses 1 AI+ credit once approved. On a Full control connection it starts at once; otherwise it returns a confirmationId and waits for the owner's yes.

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

Input Schema

Name	Required	Description
`prompt`	No	What should move in the scene, like 'water ripples in the pool'.
`photoId`	Yes	A photo: its photoId from the edit summary, or its play position like "shot 3".
`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 / prompt / description
```
Added value: +"What should move in the scene, like 'water ripples in the pool'."
```
First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Adds substantial context beyond annotations: 1 AI+ credit consumed only on approval, immediate execution on Full control connections, and a confirmationId wait otherwise. It stops short of disclosing what happens to an existing AI+ version on the shot, which matters given destructiveHint=true.

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 tight sentences, front-loaded with purpose, then camera constraint, then cost and approval flow. Every sentence carries decision-relevant information with no filler.

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?

An output schema exists, so return values needn't be explained, and the description covers cost, approval, and the camera limitation. The main gap is the absence of any statement about overwriting or replacing an existing AI+ motion on a shot, relevant to the destructive annotation.

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 coverage is 100%, so baseline is 3. The description reinforces the prompt's intent (name scene motion, not camera) but adds no format or constraint detail for photoId or listingId beyond what the schema already documents.

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?

States a specific verb and resource ("Generates cinematic AI motion for one shot") with concrete examples of what moves. It implicitly contrasts with multi-shot motion via "one shot" and the fixed camera note, but never names a sibling to distinguish against.

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

Usage Guidelines3/5

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

Explains how to use it (the prompt names what moves, not a camera move) and notes the approval path, but gives no explicit when-to-use vs when-to-prefer-an-alternative guidance relative to request_ai_seamless or regenerate_ai_version.

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?