Reel-E

Reorder shots

reorder_shots

Destructive

Set the full play order. List every current shot exactly once.

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>",
      "order": "<order>"
    },
    "name": "reorder_shots"
  }
}

Input Schema

Name	Required	Description	Default
`order`	Yes	Every current shot exactly once, in the new play order.
`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 / order / description
```
Added value: +"Every current shot exactly once, in the new play order."
```
First observedNov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is covered structurally. The description adds value by establishing whole-list replacement semantics, but it never says what happens to shots omitted from the list or whether the change is reversible — precisely the facts an agent needs before invoking a destructive reorder.

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?

Two short sentences with the operation front-loaded and the key constraint second; nothing is padded and no sentence repeats another.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need no explanation, and annotations cover the safety profile. For a destructive, non-idempotent whole-list replacement, though, the omission-handling behavior is a real gap that leaves the agent guessing about data loss.

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%, including the photoId-or-"shot 3" item format and the 1–75 bounds, so the schema carries parameter meaning. The description largely restates the order field's own schema text ("every current shot exactly once") and adds no new format or validation detail, warranting the baseline 3.

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?

"Set the full play order" names a specific verb and resource, and "List every current shot exactly once" pins down the replacement semantics, distinguishing it from an incremental reorder. It stops short of naming a sibling such as move_shot as the single-shot alternative, so 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?

The phrase "full play order" plus "every current shot exactly once" implicitly tells the agent this is the bulk/replacement path rather than a one-shot move, but no alternative tool or when-not-to-use condition is named. Usage is inferable, not spelled out.

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?