Reel-E

Record one part again

rerecord_narration_section

Destructive

Record only one part of the narration again, keeping the other parts' audio, the same as re-recording one block in the Voiceover panel. Uses 1 voice generation once approved. The voice stays the recording's voice: to change the voice, record the whole script (request_voiceover_audio). 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>",
      "section": "<section>"
    },
    "name": "rerecord_narration_section"
  }
}

Input Schema

Name	Required	Description	Default
`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.

First observedNov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses the credit cost ('Uses 1 voice generation once approved'), the non-Full-control approval flow returning a confirmationId, and the crucial side effect that the existing voice is preserved rather than re-selected. The annotations only flag destructive/non-idempotent; the description tells the agent what is actually destroyed and what is preserved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with what the tool does, followed by cost, voice-retention constraint, and approval behavior. No redundant restatement of the title or name.

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 mutating, credit-consuming operation the description covers cost, approval gating, and preservation of untouched audio, and an output schema exists so return values need no explanation. An agent has everything needed to invoke it correctly and predict the confirmation flow.

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 (section, listingId) are already documented in the schema and the baseline of 3 applies. The description adds only a light restatement that a single part is targeted, not any new format or selection semantics for 'section'.

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?

States a specific verb and resource with precise scope: 'Record only one part of the narration again, keeping the other parts' audio.' It also names the full-script sibling (request_voiceover_audio), so the agent can distinguish partial re-record from a whole-script voiceover 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?

Explicitly gives the condition for using the alternative: 'to change the voice, record the whole script (request_voiceover_audio).' It also explains the approval branch (starts at once on Full control, otherwise confirmationId). The one gap is that the nearby sibling edit_narration_section is never mentioned, so the edit-vs-rerecord choice is left to inference.

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?