Skip to main content
Glama
Sign In

Reel-E

by ai.reel-e
OverviewDiscussionsAdmin

Add photos to a new listing

add_listing_photos
DestructiveIdempotent

Adds photos to a draft: photos attached in the chat (where the app supports it), the photos the listing link import found (useImportedPhotos), files uploaded with request_photo_upload (uploadIds, up to 12), and/or https image links (urls, up to 12 per call). JPG, PNG, WebP or HEIC, up to 25 MB each. Sending the same photo again adds nothing twice, so repeated calls continue until notYetAdded is 0. A listing needs at least 3 photos; the account's photo limit decides how many appear in the video, and the rest stay in the listing gallery.

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

Input Schema

NameRequiredDescriptionDefault
urlsNohttps image links to the person's own photos (JPG, PNG, WebP or HEIC), up to 12 per call.
photosNoPhotos attached in the chat.
draftIdYesThe draftId start_listing returned.
uploadIdsNouploadIds from request_photo_upload whose files were already sent, up to 12.
useImportedPhotosNotrue adds the photos the listing link import found.

Output Schema

NameRequiredDescriptionDefault
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / photos
      Added value: +{
+  "description": "Photos attached in the chat.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "download_url": {
+        "type": "string"
+      },
+      "file_id": {
+        "type": "string"
+      },
+      "file_name": {
+        "type": "string"
+      },
+      "mime_type": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "download_url",
+      "file_id"
+    ],
+    "type": "object"
+  },
+  "maxItems": 12,
+  "type": "array"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / uploadIds / description
      Added value: +"uploadIds from request_photo_upload whose files were already sent, up to 12."
    • addedInput schema / properties / urls / description
      Added value: +"https image links to the person's own photos (JPG, PNG, WebP or HEIC), up to 12 per call."
    • addedInput schema / properties / useImportedPhotos / description
      Added value: +"true adds the photos the listing link import found."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare non-read-only, idempotent, open-world, and destructive behavior. The description adds substantial operational context beyond them: supported formats, 25 MB per-file limit, deduplication semantics with notYetAdded, the minimum 3-photo requirement, and how the account photo limit affects video vs gallery placement. It does not explain the destructiveHint or return shape, but the output schema covers returns.

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?

The description is dense but well organized, starting with purpose and then layering source options, technical constraints, dedupe behavior, and minimum-count rules. Some clauses are long, but each sentence carries useful operational information with no filler.

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 five-parameter draft mutation with an output schema and rich annotations, the description covers the critical invocation details: valid sources, per-call limits, accepted formats, file size, idempotent retry behavior, and the minimum photo requirement. An agent has enough information to call this correctly without needing to infer missing prerequisites.

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%, and each of the five parameters has its own schema description. The prose reinforces which source maps to which parameter and repeats the 12-item limits, but it adds little semantic detail beyond what the schema already provides, so the baseline 3 is appropriate.

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?

The description opens with a specific verb and resource: 'Adds photos to a draft.' It then enumerates the supported photo sources, making clear this is the draft-listing photo-addition tool rather than a generic upload or edit tool.

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?

The description establishes when to use it (on a draft) and explains the four valid input paths, including that uploadIds depend on request_photo_upload. It does not explicitly contrast with the sibling add_photos tool or state when not to use this tool, so it falls short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Reel-E toolsInspect
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