Reel-E

Get an upload link for a photo

request_photo_upload

Destructive

For a photo file on the assistant's own machine: returns an uploadUrl. The file's bytes are PUT there with the returned headers within 10 minutes, and the uploadId then goes to add_listing_photos.

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": {
      "draftId": "<draftId>",
      "filename": "<filename>",
      "mimeType": "<mimeType>",
      "size": "<size>"
    },
    "name": "request_photo_upload"
  }
}

Input Schema

Name	Required	Description
`size`	Yes	The file's size in bytes (at most 25 MB).
`sha256`	No	Optional: the file's SHA-256, lowercase hex.
`draftId`	Yes	The draftId start_listing returned.
`filename`	Yes	The photo file's name, like 'living-room.jpg'.
`mimeType`	Yes	The file type: image/jpeg, image/png, image/webp, image/heic or image/heif.

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 / filename / description

Added value: +"The photo file's name, like 'living-room.jpg'."

addedInput schema / properties / mimeType / description

Added value: +"The file type: image/jpeg, image/png, image/webp, image/heic or image/heif."

First observedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already flag the mutation profile (readOnlyHint=false, destructiveHint=true), but the description adds genuinely new behavior: a hard 10-minute validity window, the requirement to PUT to the URL with the returned headers, and the uploadId handoff. It does not explain why the operation is marked destructive (e.g. link expiry, draft state impact), leaving some annotation context unexplained.

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 tight sentences with zero filler, and the primary output (uploadUrl) is front-loaded before the follow-up procedural steps. Every clause conveys actionable information.

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?

Because an output schema exists, return values need not be explained, and the description covers the key constraint an agent would otherwise get wrong: the 10-minute upload window and the uploadId handoff. It could say more about failure modes (expired link, size rejection) or whether a new link invalidates a prior one.

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 description coverage is 100%, with size limits, mimeType enum, and the draftId origin all documented inline, so the schema carries the parameter burden. The description adds only the implicit constraint that the file must live on the assistant's machine; it adds no format or syntax detail beyond the schema.

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 ('returns an uploadUrl' for 'a photo file on the assistant's own machine'), and the 'own machine' qualifier scopes it away from generic upload siblings. It also names the downstream consumer, add_listing_photos, which lets an agent place the tool in the pipeline without opening a 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?

It gives clear workflow context — PUT the bytes to the returned URL with the returned headers within 10 minutes, then pass the uploadId to add_listing_photos — so the agent knows when this step is appropriate. It stops short of stating explicit exclusions or contrasting alternatives like upload_media or request_photo_edit.

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?