Reel-E

Add new photos

add_photos

Destructive

Add photos the person attached (attachment storageIds) to the listing and, by default, to the video at a 1-based position (default: the end).

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

Input Schema

Name	Required	Description
`toVideo`	No	False keeps them in the library only.
`position`	No	1-based place in the play order; default is the end.
`listingId`	Yes	Listing id from list_listings.
`storageIds`	Yes	Photos uploaded with upload_media or attached in the chat (their storageIds).

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

Added value: +"1-based place in the play order; default is the end."

addedInput schema / properties / storageIds / description

Added value: +"Photos uploaded with upload_media or attached in the chat (their storageIds)."

First observedNov 9, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, so the safety bar is lower. The description adds real context about the default dual-write (listing plus video) and the default insertion position, but it never explains why the operation is destructive — e.g. whether inserting at a position displaces or replays existing photos — which is the one behavior an agent most needs to know before calling it.

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?

A single dense sentence that front-loads the action and the target, with the important default stated early. It is efficient, though the parenthetical nesting makes it slightly harder to scan than a two-clause split would be.

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 not be explained, and the annotations carry the safety profile. However, for a destructive, non-idempotent, multi-parameter mutation with a near-identical sibling tool, the definition omits the consequences of the default video write and any guidance on choosing between the two add-photo tools.

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 baseline is 3. The description restates the position default ('the end') and the toVideo default ('by default, to the video'), adding marginal interpretation beyond the schema but no new meaning such as ordering conflicts or the 20-item cap.

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?

The description states a specific verb and resource ('Add photos ... to the listing and ... to the video') and clarifies the source of the identifiers (attachment storageIds). It is clear what the tool does, but it never distinguishes itself from the similarly named sibling add_listing_photos, leaving the agent to guess which one applies.

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?

Usage is only implied: the phrase 'by default, to the video' and the schema note 'False keeps them in the library only' hint at the two modes, but there is no explicit statement of when to choose this tool over add_listing_photos or add_shots. No prerequisites or exclusions are given.

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?