Reel-E

First cut on the drop

align_first_cut_to_drop

Destructive

Starts the song at the point that makes the video's first cut land exactly on the drop (checked with the Studio's own timing, within one frame); later cuts stay on the beat grid. It uses the drop read_music_structure reports, by trimming the song's start (the person's own uploaded or generated tracks only). Uses no credit; undoable. A track still being made or analysed reports that, and the alignment can be done once the track is ready.

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

Input Schema

Name	Required	Description	Default
`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.3/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 cost (no credit), reversibility (undoable), the exact mutation performed (trimming the song's start), and the eligibility constraint (own uploaded or generated tracks only). It also describes behavior when the track is not yet ready, which is the kind of precondition an agent needs before calling a destructive operation.

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?

Front-loads the core effect in the first clause, then layers cost, reversibility, and preconditions. The parentheticals ('within one frame', 'own uploaded or generated tracks only') are dense but each carries real constraint information, though the sentences run long.

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?

For a destructive, single-parameter mutation with an output schema, the description covers cost, reversibility, data source, scope limits, and not-ready behavior. Only a note on ambiguous cases (e.g. multiple drops) or how a successful alignment is reported back 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 coverage is 100% and there is a single required listingId already documented as coming from list_listings. The description adds no further meaning about the parameter, so the baseline of 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 action and outcome: starting the song so the video's first cut lands on the drop, with later cuts staying on the beat grid. It is clearly distinct from siblings like trim_music and read_music_structure, the latter being named as the source of the drop data.

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?

Explains the precondition (the drop comes from read_music_structure) and the failure case (a track still being made or analysed reports that, and alignment can be done once ready). It also restricts scope to the person's own uploaded or generated tracks. It stops short of an explicit 'use trim_music instead when...' routing statement, but the context is clear.

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?