Reel-E

Shot length

set_shot_length

Destructive

How long shots stay on screen. Cuts land on the music's beats, so length is shorter (half), normal or longer (double). The first and last shots have set lengths: a shorter first shot while the opening title is on, or a shorter ending, comes back as a choice for the person (remove the title or an end card, or keep it).

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>",
      "photoIds": "<photoIds>",
      "length": "<length>"
    },
    "name": "set_shot_length"
  }
}

Input Schema

Name	Required	Description
`length`	Yes	shorter (half), normal or longer (double), on the music's beats.
`photoIds`	Yes	The shots: each a photoId from the edit summary, or a play position like 'shot 3'.
`listingId`	Yes	Listing id from list_listings.

Output Schema

Name	Required	Description	Default
`status`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

addedInput schema / properties / length / description

Added value: +"shorter (half), normal or longer (double), on the music's beats."

addedInput schema / properties / photoIds / description

Added value: +"The shots: each a photoId from the edit summary, or a play position like 'shot 3'."

First observedNov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds genuinely non-obvious behavior: the first and last shots have fixed lengths, and a conflicting shorter opening/closing returns as a choice for the person (drop the title or end card, or keep it). That 'this may come back as a user decision' signal is valuable context an agent could not get from the annotations. It does not explain why the operation is destructive or what state gets overwritten, which keeps it out of 5 territory.

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 core behavior is front-loaded in the first sentence and there is no filler. The second sentence is dense and slightly tangled in its phrasing about titles and end cards, but every clause carries real information about the edit's edge behavior.

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?

A 3-parameter required-only mutation tool with full schema coverage and an output schema, so return values need no explanation. The description covers the value scale and the notable edge-case prompting behavior; only the destructive/irreversibility angle flagged by annotations goes unaddressed.

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, and the description earns an extra point by explaining what 'shorter' and 'longer' concretely mean (half / double, snapped to music beats) and by warning that the first and last entries in photoIds are subject to fixed lengths — a constraint on how to pick those IDs that the schema does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states clearly what the tool controls: 'How long shots stay on screen' and the three-length scale (half / normal / double) tied to music beats. An agent can distinguish it from set_shot_speed and set_pace by the concept of duration rather than speed or overall pacing, though the differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: an agent infers you call this when the user wants shots held longer or cut faster. No explicit when-to-use or when-not guidance, and no named alternative (set_shot_speed, set_pace) despite those siblings sitting adjacent to this one.

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?