Skip to main content
Glama

woo_amazon_mapping

Read-only

READ-ONLY. Maps WooCommerce products to the Amazon catalog of an outpost (account_id): same SKU in the Amazon catalog (data-hub), and with lookup_ean=true the EAN/GTIN searched in the Amazon catalog (max 20 EANs per call). Shows matched, unmatched, items without SKU or EAN. Changes nothing on either side.

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": {
      "store_id": "<store_id>",
      "account_id": "<account_id>"
    },
    "name": "woo_amazon_mapping"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax WooCommerce products (default 200, cap 500)
store_idYesId negozio WooCommerce (da woo_list_stores).
account_idYesAmazon outpost (seller × marketplace) from list_clients
lookup_eanNoAlso search unmatched EANs in the Amazon catalog (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / store_id / description
      Added value: +"Id negozio WooCommerce (da woo_list_stores)."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'READ-ONLY' and 'Changes nothing on either side' rather than contradicting it. Beyond the annotations it adds real behavioral context: what the result distinguishes (matched, unmatched, no SKU, no EAN) and the 20-EAN-per-call ceiling.

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?

It is a compact two-part statement with the safety flag and core purpose front-loaded, and every clause carries information. It is slightly dense and reads as a single run-on sentence, which costs a point versus a cleaner structure.

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 takes on the burden of describing results and does so by enumerating the four outcome categories. Combined with the read-only guarantee, the EAN cap, and full schema coverage, 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%, so the baseline is 3, but the description adds meaning the schema lacks: account_id is characterized as an 'outpost', the EAN lookup is explicitly tied to the Amazon catalog data-hub, and a per-call cap of 20 EANs is stated that appears nowhere in 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?

The description opens with a specific verb and resource ('Maps WooCommerce products to the Amazon catalog of an outpost') and then narrows the matching rule to SKU and optionally EAN/GTIN. It is instantly distinguishable from siblings like woo_list_products or ads_catalog_coverage, which list or report rather than map.

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?

It gives a clear condition for the optional mode ('with lookup_ean=true the EAN/GTIN searched in the Amazon catalog') and states a practical limit (max 20 EANs per call). It does not name an alternative tool for when mapping is not the right approach, so it stops short of full when/when-not guidance.

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