Reel-E

Use the person's own narration words

draft_narration

Destructive

Lays out the exact words the person typed or dictated ('say: Welcome to 12 Oak Lane...') over the shots as the listing's draft script, in the Voiceover panel, without spending anything. The person's words go in play order, one part per shot or pair of shots, as written; a part with more words than its shots leave time for is shortened to fit (a part over more shots, with toShot, keeps more words), and wording that could break fair-housing rules is replaced. The reply lists the exact saved words of every part and says which changed, so the person can read them before recording. A script written for the person comes from request_voiceover_script, the script writer that watches the video.

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

Input Schema

Name	Required	Description
`language`	No	The script's language: en (English) or es (Spanish).
`sections`	Yes	The person's words in play order, one part per shot or run of shots.
`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 / language / description

Added value: +"The script's language: en (English) or es (Spanish)."

addedInput schema / properties / sections / description

Added value: +"The person's words in play order, one part per shot or run of shots."

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, it discloses non-obvious behavior: no credits are spent, over-long parts are shortened to fit shot timing, fair-housing-problematic wording is replaced, and the reply enumerates the exact saved words and flags which changed. These are exactly the mutation consequences an agent needs to warn a user about for a destructive, non-idempotent write.

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 core action and the no-cost guarantee, then consequences, then the return shape, then the alternative. Sentences are long and densely parenthetical, which costs a bit of readability, but nothing is redundant.

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?

Despite an output schema existing, the description still summarizes the reply's key property (exact saved words plus change flags), and it covers mutation side effects, cost, and sibling routing. Nothing an agent needs to call this destructive write 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 already 100%, but the description adds real meaning: parts are placed in play order one per shot or run of shots, and a part spanning more shots via toShot retains more words when truncation occurs. That explains the timing/truncation interaction the schema only hints at, though it does not explain the language parameter.

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 states a specific verb and resource: it lays out the person's own typed/dictated words as the listing's draft script in the Voiceover panel. It explicitly distinguishes itself from the sibling request_voiceover_script, which produces an AI-written script, so an agent can route without opening either 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?

It establishes the selection condition clearly: use this when the person's own words are the source, and use request_voiceover_script when a script must be written for them. It gives no explicit 'do not use when' exclusions (e.g., existing recorded narration), so it stops short of a 5.

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?