Reel-E

Make a download

request_download

Destructive

Where the person downloads the video in one format (16:9, 1:1 or 9:16): downloads are made in Reel-E, so this returns the listing page link (and the editor's) for the owner. Nothing renders from this call.

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

Input Schema

Name	Required	Description
`aspect`	Yes	The format: 16:9 (wide), 1:1 (square) or 9:16 (vertical).
`branded`	No	true for the version with the title and contact card; false for unbranded.
`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 / aspect / description

Added value: +"The format: 16:9 (wide), 1:1 (square) or 9:16 (vertical)."

addedInput schema / properties / branded / description

Added value: +"true for the version with the title and contact card; false for unbranded."

First observedNov 9, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety bar is lowered. The description usefully adds that no rendering occurs and that the return is a listing page link plus the editor link, but it never explains what the destructive hint refers to or whether a download record is created. That leaves the most consequential behavioral question unanswered.

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?

Compact, two-clause structure with no padding. The phrasing is slightly awkward and the key fact (returns links, does not render) is buried after the aspect list rather than front-loaded.

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?

An output schema exists, so return shape need not be explained, and annotations cover the safety profile. The description supplies the non-obvious facts an agent needs — no render, links returned — leaving only the meaning of destructiveHint and sibling routing unaddressed.

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 the schema already documents aspect (with enum), branded and listingId. The description only restates the three aspect values and says nothing about branded or listingId, so it adds no meaning beyond the schema.

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

Purpose3/5

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

The description conveys that this is the entry point for a download in a chosen aspect ratio and that it returns listing/editor links rather than a file. However, the phrasing 'Where the person downloads the video' is indirect about what the tool actually triggers, and it never distinguishes itself from sibling request_* tools. Purpose is inferable but not stated as a clean verb+resource.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the many request_* siblings. The only directional signal is the negative statement 'Nothing renders from this call,' which clarifies outcome but not selection.

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?