Reel-E

Change a narration part

edit_narration_section

Destructive

Changes the words of one part of the draft script (section: its 1-based number in the Voiceover panel, or its id), the same save as the Voiceover panel's section editor. Uses no credit; undoable. A recorded voice keeps the old words until that part is recorded again (rerecord_narration_section).

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>",
      "section": "<section>",
      "text": "<text>"
    },
    "name": "edit_narration_section"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	The part's new words, up to 600 characters.
`section`	Yes	Part number (1 = first) or id.
`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 / text / description
```
Added value: +"The part's new words, up to 600 characters."
```
First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond annotations, the description discloses that the edit uses no credit and is undoable, and that recorded audio retains old words until the section is rerecorded. Those are meaningful operational details not present in the structured annotations, especially for a destructive mutation.

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 definition is front-loaded and uses three tight sentences. The parenthetical section explanation is useful but partly duplicates schema content, keeping it just below maximally concise.

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?

The description covers the mutation's effect, undoability, credit behavior, and the recorded-voice caveat, which is enough given full schema coverage and an output schema. Minor details like precise output shape are appropriately left to structured fields.

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%, and the schema already explains listingId, section, and text. The description restates that section is a 1-based number or id, but adds little parameter meaning beyond the schema.

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: 'Changes the words of one part of the draft script.' It also clarifies the section identifier semantics and distinguishes the action from rerecording a voiceover, so an agent can identify the tool without opening the 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 clear implied usage: edit draft script text via the same save as the Voiceover panel. It also names rerecord_narration_section as the alternative when a recorded voice must reflect new words, though it stops short of an explicit when-not-to-use instruction.

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?