Skip to main content
Glama

Add photos to a listing

add_listing_photos

Adds photos to one of your seller products, from public https links to PNG or JPG images (up to 10 MB each) or from images the user attached, where the app passes attached files to tools. New photos go after the ones already on the listing; none is removed or reordered. A listing holds 6 photos. Only seller products from list_my_listings. Needs a connected Printlooper account.

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

Input Schema

NameRequiredDescriptionDefault
listing_idYesA seller product id from list_my_listings (prd_...)
photo_urlsNoPublic https links, each downloading one PNG or JPG image (a direct link to the file, not a web page)
photo_filesNoImages the user attached, as the file objects an app passes to tools. Leave out when you have no download_url for an image

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / photo_files / description
      Previous value: -"Images the user attached in ChatGPT"New value: +"Images the user attached, as the file objects an app passes to tools. Leave out when you have no download_url for an image"
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses the genuinely useful behaviors: new photos are appended after existing ones, nothing is removed or reordered, each image is capped at 10 MB, and a listing holds 6 photos. It does not say what happens when the 6-photo cap is exceeded or what the call returns, which are the remaining behavioral gaps.

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 content is dense and front-loaded, with the core action and accepted sources stated first and constraints following. The single long opening sentence is somewhat run-on, and the standalone fragment 'A listing holds 6 photos.' reads abruptly, but no sentence is wasted.

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?

For a 3-parameter mutation tool with no output schema, the description covers sources, limits, ordering behavior, prerequisites, and the id source. What remains missing is the outcome of the call (what is returned, or what error occurs when the 6-photo limit is hit), which an agent would want before invoking it.

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: links must be direct file links to PNG/JPG (not web pages), a 10 MB per-image cap that appears nowhere in the schema, and the ordering semantics of appended photos. The file-object parameter is only described as 'images the user attached', which the schema already covers.

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 opens with a specific verb and resource ('Adds photos to one of your seller products') and enumerates the two accepted sources (public https links or user-attached files). It is clear what the tool does, but it never distinguishes itself from the similarly named sibling add_product_photos, leaving the agent to guess which photo-adding tool applies.

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?

Prerequisites are stated plainly: the listing must be a seller product from list_my_listings, and a connected Printlooper account is required. It also explains the source-selection rule implicitly by describing when attached files apply. It stops short of naming an alternative or an explicit 'do not use when' condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources