Reel-E

Regenerate AI+

regenerate_ai_version

Destructive

Makes a new AI+ version of one shot for 1 AI+ credit, once approved: a VFX repeats its effect and options; natural motion repeats its prompt unless a new one is passed. version is the saved version to repeat (a number from list_ai_versions; default: the one playing now). The new version lands on the shot, undoable, and the old ones stay saved. A credit-using result's one free redo (Make again free) is the person's own button under the version after a thumbs down; it is not a tool. 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": "regenerate_ai_version"
  }
}

Input Schema

Name	Required	Description
`prompt`	No	A new prompt for natural motion; default repeats the old one.
`photoId`	Yes	A photo: its photoId from the edit summary, or its play position like "shot 3".
`version`	No	The saved version to repeat: its number from list_ai_versions; default the one playing.
`listingId`	Yes	Listing id from list_listings.

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

addedInput schema / properties / prompt / description

Added value: +"A new prompt for natural motion; default repeats the old one."

addedInput schema / properties / version / description

Added value: +"The saved version to repeat: its number from list_ai_versions; default the one playing."

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=false), it discloses the credit cost, that the result is undoable and prior versions remain saved, and the two-phase execution model: instant on a Full control connection versus a confirmationId wait for the owner's approval. That is exactly the behavioral context the agent needs and cannot get from the annotation flags.

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?

Cost, effect semantics and version default are front-loaded, and every clause carries operational information. The sentences are long and slightly run-on, with the confirmation-path caveat buried at the end, but there is no filler.

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 credit-consuming, non-idempotent mutation with an output schema, the description covers approval prerequisites, cost, invertibility, retention of old versions, and the confirmation flow that determines what comes back. Nothing an agent needs in order to call it safely 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 schema already documents all four parameters. The description still adds cross-parameter meaning the schema cannot: how the prompt is consumed depends on whether the shot is VFX (effect and options repeat) or natural motion (prompt repeats unless a new one is passed), and that version defaults to the currently playing one.

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?

The description leads with a specific verb, resource and scope: 'Makes a new AI+ version of one shot for 1 AI+ credit.' It also names what it is not (the 'Make again free' redo is a human button, not a tool) and points to list_ai_versions for the version numbering, so an agent can separate it from list_ai_versions and the free redo path.

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 states the operating condition ('once approved') and the default behavior for version ('the one playing now'), plus the VFX vs natural-motion distinction that determines whether a prompt is needed. It never explicitly routes to a sibling such as use_ai_version for switching to an existing version, so the when-not guidance is implied rather than stated.

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?