Skip to main content
Glama

Add photos to one of my products

add_product_photos

Adds photos to one variant of one of your print shop's 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. Each photo is copied into Printlooper. New photos go after the ones already on the variant; none is removed or reordered. A variant holds 6 photos. Only products from list_my_products. 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": {
      "product_id": "<product_id>"
    },
    "name": "add_product_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
photo_urlsNoPublic https links, each downloading one PNG or JPG image (a direct link to the file, not a web page)
product_idYesproduct_id from list_my_products
variant_idNovariant_id from get_my_product. May be left out when the product has one variant.
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.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that each photo is copied into Printlooper, that new photos are appended after existing ones with nothing removed or reordered (explaining destructiveHint=false concretely), and that a variant holds 6 photos. It also adds a 10 MB per-image limit, PNG/JPG-only restriction, and the auth prerequisite, none of which the annotations carry.

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?

Front-loaded with the action and densely packed with operating facts, with almost no filler. Minor redundancy: 'A variant holds 6 photos' restates the schema's maxItems of 6, and the clause about apps passing attached files is worded awkwardly.

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 mutation tool with no output schema, the definition covers source, limits, capacity, non-destructive semantics and auth, which is nearly everything needed to call it safely. It stops short of describing what is returned (created photo ids/order) or how partial failures are handled.

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: the 10 MB size cap and the PNG/JPG format requirement for photo_urls, plus the explanation that attached files are app-passed file objects. These constraints supplement the schema's bare 'uri' format rather than repeat it.

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?

States a specific verb and resource with tight scope: adds photos to one variant of one of the shop's products, accepting either https links or attached files. The scope is unambiguous, but the definition never draws the line against the sibling add_listing_photos, so an agent must infer product-photo vs listing-photo from the name alone.

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?

Gives real preconditions: only products from list_my_products, variant_id from get_my_product, and a connected Printlooper account is required. It does not state when to prefer this over add_listing_photos or what to do when the variant photo slot is already full, so exclusions are absent.

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