Skip to main content
Glama

ApparelHub

by ai.apparelhub.mcp
OverviewDiscussionsAdmin

set_product_images

Set an existing product's listing images: attach an uploaded photo or a generated lifestyle shot, reorder them, and choose the cover. Use this AFTER the product exists — create_product / ship_product pick the initial mockup themselves.

⚠️ THE LIST REPLACES, IT DOES NOT MERGE. What you send becomes the whole gallery, in the order given. To add one image, READ the current list first and send it back with the new entry in it — sending the new entry alone deletes every other image. Pass images: null to reset the gallery back to the product's provider mockups.

⚠️ ORDER IS FUNCTIONAL, NOT COSMETIC. Channels cap how many images a listing may carry and TRUNCATE IN GALLERY ORDER, so position decides what actually ships: TikTok Shop takes 9, Wix 15, Shopify and WooCommerce are unlimited. On a capped channel an image in position 10 is not a lower-priority image, it is an absent one. Put the images that must survive first. The platform stores at most 20.

Each entry carries provenance. source says where the file came from (mockup / upload / ai_mockup / print_file / unknown). ai_generated is SEPARATE and tri-state on purpose: an uploaded photo may itself have been AI-generated and the platform cannot detect that, so only you can say. Set it truthfully — true, false, or leave it unset when you genuinely do not know. Do not guess it from source.

cover sets the display image independently of order, so the cover need not be first. A cover that is not in the gallery is added to it. Replace the gallery without naming a cover and the cover follows to the new first image.

CONCURRENCY: this reads the product first and passes its version back with the write, so a change someone else made in between is REFUSED rather than silently overwritten. On a conflict the tool re-reads and returns conflict: true with the current images — it does NOT retry, because the list you built was based on a gallery that no longer exists. Rebuild from current_images and call again.

[#1d62ac]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coverNoURL of the image to show as the listing cover. Independent of gallery order. Added to the gallery if it is not already in it.
imagesNoThe COMPLETE ordered gallery, replacing whatever is there. Null resets to the product's provider mockups. Omit to change only the cover.
workspaceNoWorkspace uuid (agency accounts).
product_uuidYesThe product whose listing images to set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only supply openWorldHint, so the description carries the burden and does so richly: replace-not-merge semantics, the destructive consequence of sending a lone entry, provider truncation caps (TikTok 9, Wix 15), the 20-item platform limit, optimistic-concurrency refusal with conflict:true and no auto-retry, and cover resolution rules. This is far beyond structured data.

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?

Long but densely front-loaded: the highest-risk fact (the list replaces) is the first warning, followed by order semantics, provenance, cover, and concurrency in descending priority. Slightly heavy with warning glyphs and a trailing color token, but nearly every sentence earns its place.

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?

With no output schema, the description still tells the agent what comes back on conflict (conflict:true plus current_images) and how to proceed. Combined with the ordering/limit rules and reset semantics, an agent has everything needed to call this correctly.

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% and the schema itself already documents source and ai_generated well, but the description adds cross-parameter meaning the schema lacks: images:null resets to provider mockups, omitting images changes only the cover, cover need not sit first and is auto-added if absent, and that ai_generated must not be inferred from source. Some overlap with schema, hence not a 5.

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+resource (set a product's listing images) and immediately distinguishes itself from create_product / ship_product, which pick the initial mockup themselves. An agent can select this over siblings without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit on when to use ('AFTER the product exists'), names the alternatives that do it implicitly, and even spells out the read-then-resend workflow for adding a single image. Exclusions and prerequisites are stated, not implied.

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

All ApparelHub 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