Skip to main content
Glama

sync-new-skus

Set up Inventory Sync for one or more SKUs — the "Sync New SKU" flow of the Inventory Sync page, for a whole batch at once. Creates the entry that holds each SKU's stock, records the on-hand quantity, and links every active listing and variation carrying that SKU to it.

This is the Inventory Sync tool, NOT the Product Catalog: use it for accounts that manage stock without the catalog. The entries it creates are internal and will not show up in get-products. Do not use create-product for this — that builds a real catalog product, which is not what Inventory Sync reads.

onHandQuantity is required for every SKU: the quantity is pushed out to every listing carrying that SKU, so there is no safe default. Idempotent — calling again relinks the existing entry instead of creating a duplicate. SKUs that match no active listing or variation are reported and the batch refused, unless ignoreUnmatched is set; run with dryRun: true first to check. Authenticated via bearer token.

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": {
      "items": "<items>"
    },
    "name": "sync-new-skus"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesThe SKUs to sync, each with its own quantity
dryRunNoReport the resolution without writing anything
sellerIdsNoAccounts to link across. Defaults to every account with Inventory Sync on; one with it off is refused.
ignoreUnmatchedNoCreate entries for SKUs matching no listing anyway

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations: discloses that entries are internal and invisible to get-products, that the call relinks rather than duplicates (idempotent), that the whole batch is refused on unmatched SKUs, and that auth is via bearer token. The only real gap is what the refusal/report payload actually looks like, which matters since there is no output schema.

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 purpose, then differentiation, then per-parameter cautions — a logical order with no filler paragraphs. There is minor restatement (onHandQuantity being required is already in the schema) but nothing that costs an agent comprehension.

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?

For a mutating, batch, nested-item tool with no output schema, the definition covers scope, side effects, idempotency, refusal behavior, dry-run verification, and auth — everything needed to invoke it safely without guessing.

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 baseline is 3, and the description earns an uplift by explaining why onHandQuantity has no default (it is pushed out to every listing carrying the SKU) and by tying dryRun and ignoreUnmatched to concrete workflows. sellerIds semantics are left entirely to the schema.

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?

Names a specific verb and resource ("Set up Inventory Sync") plus the exact UI flow it mirrors and the batch scope. It explicitly distinguishes itself from the Product Catalog, get-products, and create-product, so an agent can pick it over siblings without reading schemas.

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?

Gives explicit when-to-use (accounts managing stock without the catalog), when-not-to-use (do not use create-product), and an operational prerequisite (run with dryRun: true first). It also states the failure condition and the ignoreUnmatched escape hatch, leaving little to inference.

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.