Skip to main content
Glama
Sign In

Obriym CRM

by com.obriym-crm
OverviewDiscussionsAdmin

Check a model with variations for Amazon

check_amazon_variation_family
Read-only

The model's active articles not yet on Amazon become ONE listing with variations — 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. Every listing is first validated by Amazon (VALIDATION_PREVIEW); this tool only checks and creates nothing. Start from gaps: one entry per kind of problem with every SKU it concerns, found before Amazon is asked — size or color (set with update_product), price (none in the run's currency, the marketplace's: upsert_product_prices, set_product_channel_price or apply_bulk_price_change), productType (update_category), brand, images, condition, title; quantity with blocking=false: the article does not track stock, so the listing goes up without one (update_product with trackInventory, then adjust_stock); and barcodeLength with blocking=false: the article's barcode has another number of digits than the rest of the model, so a digit may be lost — confirm it from the label before publishing (update_product with ean). Amazon is asked only when no gap blocks. Also returns parentSku, theme, currency, blocker (tooFewArticles, noAxis, missingAxisValue, duplicateCombination, themeUnsupported, parentSkuTaken, parentTitleTooLong, tooManyArticles — the last is this CRM's limit for one run, not Amazon's: never suggest splitting the model), fieldProblems (what the product type still needs per Amazon's schema, once per field: attribute key, title in the marketplace's language, kind missing or invalid, allowed values with labels, units, the SKUs concerned, and for an attribute made of several values its parts: each part's key attribute.part, title, required, allowed values and unresolved — true when neither a person nor the CRM has an answer for it), parentIssues, children per article (missing, quantity, barcode, Amazon's sentences, status; notChecked = Amazon did not get to it, call again — what passed is kept for an hour while the article's data stays the same, so each call only checks the rest) and skipped articles (already on Amazon, taken off the channel). The CRM fills model_name, list_price, the dimensions and a size attribute (from each article's own size, with its system and class) itself; set any other field, or a part reported as unresolved, with set_amazon_field_values on the model (every article inherits it) — keys and values from get_amazon_fields. Then create it with publish_amazon_variation_family.

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": "check_amazon_variation_family"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelIdYesA product model id (the model a product's modelId points at; get_product shows it).
marketplaceIdNoOne 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / marketplaceId
      Added value: +{
+  "description": "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.",
+  "maxLength": 32,
+  "minLength": 1,
+  "type": "string"
+}
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Well beyond the annotations, which already declare readOnlyHint=true and destructiveHint=false, the description discloses that validation happens server-side on Amazon, that passing results are cached for an hour while article data is unchanged, that notChecked means Amazon did not reach the article, and that tooManyArticles is a CRM run limit rather than an Amazon rule with an explicit instruction never to suggest splitting the model. It also enumerates the blocker codes and the fieldProblems/unresolved semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is largely load-bearing, but it is delivered as one ~350-word run-on paragraph braided with em-dashes, semicolons and inline enumerations, with no headings or line breaks. The single most important sentence ("this tool only checks and creates nothing") is buried in the middle, so the definition is neither front-loaded nor scannable despite the value of its information.

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?

There is no output schema, and the description compensates fully by enumerating the return surface: parentSku, theme, currency, the blocker code list, fieldProblems with per-attribute parts and allowed values, parentIssues, per-child status with notChecked semantics, and skipped articles. For an open-world read-only validation tool with only two parameters, an agent has everything needed to call it and interpret the result.

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 coverage is 100% and both parameters are documented in the schema itself, including the get_product cross-reference and the omit-for-main-store default, so the baseline is 3. The description adds only marginal parameter context — the marketplace's currency and the fact that each store holds its own family in its own language — without new syntax or format detail.

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 makes the operation specific — it groups a model's active articles into one Amazon variation family and only validates it: "Every listing is first validated by Amazon (VALIDATION_PREVIEW); this tool only checks and creates nothing." It clearly separates itself from publish_amazon_variation_family and update_amazon_variation_parent. The only weakness is placement: the first sentence describes the resulting listing structure rather than the check action, so the actual purpose arrives mid-paragraph.

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?

It gives an explicit workflow: start from the gap report, resolve each gap type with a named tool (update_product for size/color, upsert_product_prices or set_product_channel_price or apply_bulk_price_change for price, update_category for productType, set_amazon_field_values for other fields), and only then call publish_amazon_variation_family. It also states the precondition ("Amazon is asked only when no gap blocks") and what to do on notChecked — call again, since passed results are cached for an hour.

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

All Obriym CRM 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