Reel-E

Put narration in the video

apply_narration

Destructive

Puts the recorded narration into the video, or takes it out (enabled false). The person normally does this with Apply in the Voiceover panel after hearing it; this tool covers a request in words ('turn the narration on', 'put it in', 'take it out'). While a voice is still being recorded it is queued, and the recording goes in as soon as it finishes. Captions are separate (set_captions).

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": "apply_narration"
  }
}

Input Schema

Name	Required	Description	Default
`enabled`	No	False takes the narration out of the video.
`listingId`	Yes	Listing id from list_listings.

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=false, and the description adds genuinely new behavior: while a voice is still being recorded the request is queued and applied when the recording finishes. That queuing detail is not derivable from any structured field. It stops short of saying whether taking narration out discards the recorded audio or just detaches it, which matters for a destructive-flagged tool.

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?

Three sentences, front-loaded with the core action and the on/off polarity before the workflow context. Every sentence carries information; the phrasing is slightly conversational ('The person normally does this with Apply...') but it earns its place by grounding the tool in the human workflow.

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?

With an output schema present, return values need no explanation, and the description covers the mutation, the toggle semantics, the async queuing case, and the sibling boundary. The only missing piece is what happens to an already-recorded narration when it is taken out, which is relevant given destructiveHint=true.

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%, so both parameters are already documented, including enabled=false. The description restates the enabled=false meaning and implies enabled defaults to 'on' via 'takes it out (enabled false)', but adds no new syntax or constraint information. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 opens with a specific verb and resource: 'Puts the recorded narration into the video, or takes it out (enabled false).' It immediately distinguishes itself from the caption sibling with 'Captions are separate (set_captions)', so an agent can separate this from set_captions or draft_narration without opening a 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 gives a concrete use context — the user asking in words ('turn the narration on', 'put it in', 'take it out') — and names the manual equivalent (Apply in the Voiceover panel). It also rules out captions explicitly. It does not, however, contrast with the adjacent narration tools (edit_narration_section, rerecord_narration_section, draft_narration), which is a gap.

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?