Reel-E

Write the narration script

request_voiceover_script

Destructive

Keylight's script writer for any narration or voiceover request ('add a voiceover', 'write narration', 'rewrite the script'), the same as Generate auto voiceover in the Voiceover panel: it watches the video and writes a script timed to the shots. Uses 1 script generation once approved (the reply says how many are left); the draft then appears in the Voiceover panel to read, edit, hear in any voice and record. For the person's own exact words, draft_narration is the 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>"
    },
    "name": "request_voiceover_script"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	The script's language: en (English) or es (Spanish).
`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 / language / description
```
Added value: +"The script's language: en (English) or es (Spanish)."
```
First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Adds substantial context beyond the annotations: it consumes one script generation once approved, the reply reports the remaining count, and the draft lands in the Voiceover panel where it can be read, edited, voiced and recorded. It also discloses the two execution paths (immediate vs. confirmationId-gated). The one gap is that destructiveHint=true is never explained – the description never says whether an existing script is replaced, despite 'rewrite the script' being listed as a trigger.

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?

Purpose and trigger phrasings are front-loaded, and the alternative tool plus the confirmation behavior follow in a logical order; nearly every clause carries distinct information (quota, panel destination, control-mode branching). It is a dense single paragraph, though, and the 'the same as Generate auto voiceover in the Voiceover panel' analogy costs words for an agent that has no UI.

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 two-parameter, non-idempotent generation request, the definition covers cost, approval flow, output destination, and the differing behavior under Full control. With an output schema present, return-value details are already covered, and the description still explains the confirmationId meaning, so nothing an agent needs to invoke and interpret it correctly is missing.

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 description coverage is 100% with only two parameters, and both listingId and the en/es language enum are fully documented in the schema. The description adds no syntax, format, or defaulting guidance for either parameter, so the schema carries the full load – the baseline 3 applies.

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?

Names a specific verb+resource ('script writer for any narration or voiceover request') and lists concrete invocation phrasings ('add a voiceover', 'write narration', 'rewrite the script'). It also explicitly distinguishes itself from the sibling draft_narration ('For the person's own exact words, draft_narration is the tool'), so an agent can pick between them 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 Guidelines5/5

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

Gives both when-to-use triggers (paraphrased user requests) and a when-not-to-use rule that names the alternative tool and the condition selecting it (person's own exact words → draft_narration). It also states the prerequisite path: it runs immediately on a Full control connection, otherwise it returns a confirmationId and waits for the owner's yes.

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?