WEM Price Compare

Find current retailer promotions

search_promotions

Read-only

Lists current promotions (sales and offers) that retailers in WEM's Awin affiliate programmes have published, for the shopper's market. Filter by merchant or by words in the offer. Each row gives the offer, its dates and a tracked link. A promotion is not a price, and it is not a discount on a product unless its terms say it covers that product. Checkout codes are shown only where the retailer's programme lets WEM publish them; other matching promotions are counted by reason in withheld, and a withheld code may still exist. An empty result covers only these programmes, not every offer a retailer runs.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max promotions to return (default 10, max 25).
`query`	No	Words that must appear in the offer, e.g. "hoverboard" or "free delivery".
`currency`	No	ISO 4217 code for the shopper's market: GBP (default) or USD. Promotions are regional, so this decides which market's offers are read.
`merchant`	No	Retailer name, e.g. "iHoverboard". Omit for every retailer.

Output Schema

TableJSON Schema

Name	Required	Description
`more`	No	Further matching promotions beyond `limit`.
`note`	No
`count`	Yes
`links`	Yes	The tracked links from `promotions`, pre-formatted. Give these to the user when you name a promotion.
`market`	No	ISO country code the promotions were read for.
`reason`	No	Present only when no promotion is shown. None of these means the retailer has no offer on — not_configured and upstream_error mean WEM could not look.
`search`	No	Present when this result names no offer. `url` is WEM's results page for the query and `markdown` is the same link, pre-formatted. WEM searches retailers live on that page, including shops it holds no affiliate programme with, so an empty or withheld result here is not evidence the product is unavailable or unpriced.
`currency`	Yes
`withheld`	No	Matching promotions WEM did not show, counted by reason: notPublishable (a checkout code or offer the retailer’s programme does not let WEM publish; the code may well exist), notJoined, notActive, outsideMarket, noTrackedLink, otherPublisherLink, incompleteRecord.
`disclosure`	Yes	WEM’s affiliate disclosure for this answer, written to be quoted as it is. Its wording changes with the rows: it states whether every outbound link is affiliate-tracked, only some are, or none are. A version from an earlier answer may not fit this one: a row marked `affiliate: false` earns WEM nothing.
`promotions`	Yes	Ending soonest first. Each row is one live promotion WEM is allowed to show.
`withheldNote`	No	Quote this rather than paraphrase it when codes were withheld.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 4, 2026

changedInput schema / properties / currency / description

Previous value: -"ISO 4217 code for the shopper's market: GBP (default) or USD. Promotions are regional, so this decides which retailers' offers are read."New value: +"ISO 4217 code for the shopper's market: GBP (default) or USD. Promotions are regional, so this decides which market's offers are read."

changedOutput schema / properties / disclosure / description

Previous value: -"Disclosure to relay once per answer, verbatim. Its wording changes with the rows: it states whether every outbound link is affiliate-tracked, only some are, or none are. Never substitute the version you saw last time — a row marked `affiliate: false` earns WEM nothing, and saying otherwise misdescribes it to the shopper."New value: +"WEM’s affiliate disclosure for this answer, written to be quoted as it is. Its wording changes with the rows: it states whether every outbound link is affiliate-tracked, only some are, or none are. A version from an earlier answer may not fit this one: a row marked `affiliate: false` earns WEM nothing."

changedOutput schema / properties / promotions / items / properties / url / description

Previous value: -"WEM tracked redirect to the retailer’s promotion page. Relay it exactly; never rewrite it."New value: +"WEM tracked redirect to the retailer’s promotion page. The full URL; a shortened or rewritten form is a different link."

changedOutput schema / properties / search / description

Previous value: -"Present when this result names no offer. GIVE THE USER THIS LINK — it is the answer when WEM has nothing else to say, and `markdown` is ready to paste. WEM searches retailers live on that page, including shops it holds no affiliate programme with, so an empty or withheld result here is not evidence the product is unavailable or unpriced."New value: +"Present when this result names no offer. `url` is WEM's results page for the query and `markdown` is the same link, pre-formatted. WEM searches retailers live on that page, including shops it holds no affiliate programme with, so an empty or withheld result here is not evidence the product is unavailable or unpriced."

changedOutput schema / properties / withheld / description

Previous value: -"Matching promotions WEM did not show, by reason. codeNotPermitted and mentionsCode mean a checkout code WEM may not publish: the code may well exist — never say there is none."New value: +"Matching promotions WEM did not show, counted by reason: notPublishable (a checkout code or offer the retailer’s programme does not let WEM publish; the code may well exist), notJoined, notActive, outsideMarket, noTrackedLink, otherPublisherLink, incompleteRecord."

AddedSep 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly, openWorld, non-destructive), and the description adds substantial operational context: checkout codes appear only where the retailer's programme permits publication, non-publishable matches are counted in `withheld` and may still exist, and an empty result covers only these programmes rather than all a retailer runs. These are exactly the nuances an agent cannot infer from structured fields.

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 what the tool returns, then constraints, then edge cases; nearly every sentence carries distinct information. Slightly long at six sentences, but no sentence is pure filler.

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?

Given an output schema exists, the description needn't re-explain row format, yet it usefully flags that each row gives the offer, dates and a tracked link, and it covers the `withheld` edge case and empty-result semantics. Nothing needed to call it correctly is missing.

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%, so all four parameters are already documented, and the description largely restates them (currency governs the market read, merchant omitted means every retailer). It adds no new syntax or format detail beyond the schema, so the baseline 3 applies.

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 (lists) and resource (current promotions from Awin affiliate programmes), scoped to the shopper's market, and explicitly distinguishes itself from pricing tools with 'A promotion is not a price, and it is not a discount on a product.' An agent can separate this from search_products, compare_offers or find_lowest_price without opening any schema.

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?

Usable context is given: filter by merchant or words in the offer, and the boundaries ('not a price', 'not a discount unless terms say it covers that product') tell the agent when this tool is inappropriate. It stops short of naming a sibling to use instead, so it doesn't reach the explicit alternative-routing of a 5.

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

All WEM Price Compare tools Inspect

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

Need Help?