Reel-E

Find the framing

find_framing

Read-onlyIdempotent

Looks at shots with vision and works out a frame that keeps a subject in view for Wide, Square or Phone. A subject can be given ('the pool and the front door'), or left empty to frame each shot around its main subject. Returns a ready frame for each shot, which frame_shot accepts as frames; a shot where the subject can't be found, or that already shows it with the default framing, says so and gets no frame. Changes nothing. Suits any framing that depends on what is in the photo.

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

Input Schema

Name	Required	Description
`aspect`	Yes	The version the frames are for.
`subject`	No	What to keep in frame. Empty: the main subject of each shot.
`photoIds`	No	Shots to look at. Default: every shot in the video.
`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.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces this with 'Changes nothing.' More valuably, it discloses partial-failure semantics the annotations cannot: shots where the subject isn't found or already use the default framing 'say so and get no frame.' It doesn't mention cost, latency, or per-shot limits beyond the schema's maxItems.

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-loaded with what the tool does, then output coupling, then edge cases. Four dense sentences with little waste, though the closing line 'Suits any framing that depends on what is in the photo' is somewhat redundant with the opening and could be merged.

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 vision-driven, read-only computation with an output schema already present, the description covers purpose, input flexibility, downstream consumption, and no-result cases. Nothing an agent needs in order to call it correctly is missing.

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 meaning: 'subject' may be a literal phrase ('the pool and the front door') or left empty to fall back to each shot's main subject, and 'aspect' is framed as the target version. That clarifies the empty-string/default semantics more concretely than the schema's one-line hints.

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 chain: it looks at shots with vision and computes a frame that keeps a subject in view for Wide, Square or Phone. It also distinguishes itself from the sibling frame_shot by describing the hand-off ('which frame_shot accepts as frames'), so an agent can tell the two apart without opening either schema.

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?

Gives clear usage context — 'Suits any framing that depends on what is in the photo' — and implicitly contrasts with the explicit-frame path of frame_shot. It never states an explicit when-not-to-use case (e.g. use frame_shot directly when you already know the crop), so it falls short of a 5.

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?