Reel-E

Shot VFX

apply_effect

Destructive

A one-tap VFX on one shot: dusk (day to twilight), staging_fill (an empty room furnishes itself; interiors only), seasons (season_from current or a season, season_to summer, fall, winter or spring), shadows (a sun time lapse), stars (a starry night), sign_drop (3D letters drop onto the lawn: sign_text is a preset such as For Sale, Just Listed, Open House or Sold, or up to 2 words and 16 characters; default For Sale), helicopter_reveal (a helicopter lifts a cover off the home), sketch_to_real (a pencil sketch becomes the photo), house_drop (a construction time lapse) or people (a couple placed in the scene). The finished clip replaces the shot's clip, with Undo, after a few minutes. suggest_direction picks a VFX and shot for a wish; browse_options vfx lists them all. Uses 1 AI+ credit. 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>",
      "effect": "<effect>"
    },
    "name": "apply_effect"
  }
}

Input Schema

Name	Required	Description
`effect`	Yes	Which VFX; browse_options vfx describes each.
`photoId`	Yes	A photo: its photoId from the edit summary, or its play position like "shot 3".
`listingId`	Yes	Listing id from list_listings.
`season_to`	No	For seasons: the season to change to.
`sign_text`	No	For sign_drop: the sign's words, a preset like 'For Sale' or up to 2 words and 16 characters.
`season_from`	No	For seasons: the season the photo shows now, or current.
`conceptConsent`	No	true only after the person said this is for builder or concept marketing (needed for concept VFX).

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 10, 2026

addedInput schema / properties / conceptConsent / description

Added value: +"true only after the person said this is for builder or concept marketing (needed for concept VFX)."

addedInput schema / properties / effect / description

Added value: +"Which VFX; browse_options vfx describes each."

addedInput schema / properties / season_from / description

Added value: +"For seasons: the season the photo shows now, or current."

addedInput schema / properties / season_to / description

Added value: +"For seasons: the season to change to."

addedInput schema / properties / sign_text / description

Added value: +"For sign_drop: the sign's words, a preset like 'For Sale' or up to 2 words and 16 characters."

First observedNov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only say destructiveHint=true and readOnlyHint=false; the description explains what is actually destroyed ("the finished clip replaces the shot's clip"), that Undo exists, that it is asynchronous ("after a few minutes"), that it costs 1 AI+ credit, and that non-Full-control connections require owner confirmation via confirmationId.

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 core behavior (VFX applied to one shot, replaces the clip, undoable, costs a credit, confirmation flow) is front-loaded, and the effect catalog is compact despite its length. Some redundancy exists between the parenthetical effect list and the schema enum, but the glosses on each effect earn their space.

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 destructive, credit-consuming, asynchronous mutation, the description covers cost, timing, undo, approval flow, and per-effect constraints; the return shape is handled by the existing output schema, so nothing essential 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 already 100%, so the baseline is 3; the description still adds value by spelling out the sign_text presets (For Sale, Just Listed, Open House, Sold) and the staging_fill interior-only constraint. The one gap is conceptConsent, which the description never mentions, so the agent must fall back to the schema to understand the concept-VFX consent rule.

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?

Opens with a specific verb and resource ("A one-tap VFX on one shot") and then enumerates every effect with a short gloss, so an agent knows exactly what this tool produces and how it differs from suggest_direction or browse_options.

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?

Explicitly routes the agent: suggest_direction for picking a VFX from a wish, browse_options vfx for the catalog. It also states the per-effect applicability rule (staging_fill is interiors only) and the execution condition (starts at once on Full control, otherwise returns a confirmationId and waits for owner approval).

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?