Publish a model with variations on Amazon
publish_amazon_variation_familyThe model's active articles become ONE listing with variations on one Amazon store — Amazon's "variation family"; call it a model with variations when talking to the user: a parent whose SKU is the model's code (no price, no quantity) and a child listing per article, varying by colour and/or size — the theme is chosen from what the Amazon product type declares. An article not yet on the store becomes a new child (action create); an article already sold there as a listing of its own — a model put on a store article by article, or copied from another store without its parent — is JOINED to the parent (action attach): only parentage_level, child_parent_sku_relationship and variation_theme are sent to it, by PATCH under the SKU Amazon knows it by (amazonSku when that differs), and its offer, photos and texts stay as they are. A listing Amazon already shows under this parent counts as in the family (skipped, listed). Every listing is first validated by Amazon (VALIDATION_PREVIEW); only when ALL of them would be accepted is the family created — a REAL publication: the parent first, then each child with its price and quantity. Run check_amazon_variation_family first. Refused until the owner switches on AI publishing, and while listing creation is not armed on the Amazon connection; joining listings already on the store changes live listings, so it is also refused (reason amazonContentPushDisarmed) while sending content to Amazon (contentPush) is not open for that store. Returns the same report with statuses created (a new child), attached (a listing joined to the parent), excluded (a listing left out, see check_amazon_variation_family), failed, notAttempted or notChecked; each child's offer names the price, currency, quantity and fulfilment it is submitted with (quantityOmitted says why no quantity goes out), and progress says what is left (createdNow, attachedNow, alreadyOnAmazon, remaining, notReached, excluded) and the one next step: done, callAgain, fixAndRetry, fixGaps or publish. A model of about 80 articles is meant to finish in one call; a bigger one, or a slow Amazon, takes more: notChecked and notAttempted both mean the run ran out of time, so call again — a dry run an article passed is kept for an hour while its data stays the same, created and joined articles are skipped (nothing is submitted twice), the parent and the theme stay, and the rest continue. created means Amazon ACCEPTED the child for processing, not that it is live: Amazon finishes asynchronously, so check the outcome with inspect_amazon_listings and never tell the user the family is live from this result alone. The result echoes the workspace.
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": {
"modelId": "<modelId>"
},
"name": "publish_amazon_variation_family"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| modelId | Yes | A product model id (the model a product's modelId points at; get_product shows it). | |
| marketplaceId | No | One Amazon store by its id. Omit for the main store; for a write with several stores open it is required. Each store holds its own family, in its own language. |