Reel-E

Change music

set_music

Destructive

Turns the music off (musicId null), or switches to a track the person has already heard and approved, including one of this listing's generated tracks (list_generated_music). A new track goes through propose_music so the person can hear it first. Cuts re-sync to the new beat, and a track the person trimmed earlier keeps its trim. Uses no credit; undoable.

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>",
      "musicId": "<musicId>"
    },
    "name": "set_music"
  }
}

Input Schema

Name	Required	Description	Default
`musicId`	Yes	A track the person already heard and approved (list_music or list_generated_music), or null for no music.
`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 / musicId / description

Added value: +"A track the person already heard and approved (list_music or list_generated_music), or null for no music."

First observedNov 9, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Beyond destructiveHint=true and idempotentHint=false, it discloses the concrete consequences: cuts re-sync to the new beat, an existing trim is preserved, no credit is consumed, and the change is undoable. That tells the agent what is lost and what survives, which the annotations alone cannot. It stops short of stating permission requirements or any confirmation step.

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 tight sentences with the primary action front-loaded, followed by the alternative path, side effects, and cost/undo status. Every sentence carries distinct information and none is padding.

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 destructive mutation with an output schema, the agent gets the action, the required pre-approval state, the routing to propose_music, and the after-effects including undoability. Nothing needed to invoke it correctly is absent.

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 100%, so the baseline is 3, but the description adds real semantics the schema does not: musicId must reference an already-heard-and-approved track (or null to disable), and unapproved tracks require propose_music first. That validation constraint meaningfully supplements the schema's simpler 'heard and approved' phrasing.

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 (turn music off or switch tracks) with the exact mechanism (musicId null vs an approved track), and names the sibling used for the listing's generated tracks. An agent can distinguish it from propose_music and list_generated_music 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 Guidelines5/5

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

Explicitly routes the agent: a track the person has already heard and approved goes here, while a new track must go through propose_music first. It also points to list_generated_music as the source for this listing's generated tracks, so the when-to-use and when-not-to-use cases are both covered.

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?