Reel-E

Remove shots

remove_shots

Destructive

Take shots out of the video. They stay in the listing library and can come back. The video keeps at least 3 shots.

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

Input Schema

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

Changed1 schema field changedNov 10, 2026

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 declare destructiveHint=true and idempotentHint=false, so the agent already knows this mutates state. The description adds material context the annotations do not: removed shots are not deleted from the listing library and can be restored, and the operation is blocked below a 3-shot floor. It does not address idempotency or what happens if the same photoId is passed twice, which is the one gap given idempotentHint=false.

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?

Three short sentences, front-loaded with the operation, then reversibility, then the hard constraint. Every sentence carries distinct information with no restatement of the name or title.

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 two-parameter mutation with an output schema and full annotation coverage, the description supplies the two things that matter most: reversibility and the minimum-shots guard. It leaves error behavior for the 3-shot floor and for invalid photoIds unstated, but those are secondary given the output schema exists.

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%, so both parameters (listingId, photoIds) are already documented in the schema, including the photoId-or-"shot 3" addressing format and the 1-75 bounds. The description adds only the extra 3-shot floor constraint, which is real but marginal beyond what the schema provides; baseline 3 applies.

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?

"Take shots out of the video" gives a specific verb (remove) and resource (shots within a video), which is unambiguous and naturally pairs off against the sibling add_shots. It stops short of naming that counterpart or clarifying scope (e.g., per-video vs per-listing), so it is clear but not fully differentiated.

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 description implies this is a safe, reversible edit ("they stay in the listing library and can come back") and states a hard constraint ("the video keeps at least 3 shots"), which shapes when the tool can be called at all. However, it never states when to prefer this over alternatives like reorder_shots or remove_sticker, nor any prerequisites such as ownership or edit-lock state.

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?