Skip to main content
Glama

Search retail products

search_products
Read-onlyIdempotent

Search products for sale at big retailers and well-known brand stores: Myer, JB Hi-Fi, Zappos, Nike and about 180 more, deepest in Australia and US fashion. Use this when a shopper wants a product, a price check, or somewhere to buy it. Put the product in query (2 to 4 words, brand first: 'sony headphones', 'breville espresso machine') and budget, country, size and colour in their own fields. Returns ranked listings with title, store, price, availability, the retailer's product url and when it was last checked, plus retailer_search links to try when nothing matches. Prices are in each listing's own currency, exclude shipping and tax, and are not converted. No key needed. Example: {"query": "espresso machine", "country": "AU", "max_price": 600}.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
needNoOptional. What the shopper needs, in one sentence: 'quiet, fits under a 40 cm cabinet'. Not used to filter. When nothing fits, it tells exNiche exactly what is missing. No personal details.
sizeNoSize exactly as a store would list it, e.g. M, 8, 10.5. Only listings with that recorded size are returned, so leave it out for a wider search.
sortNoprice sorts need currency or country.relevance
colorNoColour as a store would list it, e.g. black.
limitNo
queryYesThe product in 2 to 4 words, brand first if the shopper named one: 'sony headphones', 'breville espresso machine', 'running shoes'. Put budget, country, size and colour in their own fields, not here.
countryNoShopper's country as a two-letter code, e.g. AU or US. Limits results to listings priced in that country's currency.
detailsNotrue = full rows (description, every matching variant). Several times larger; leave off unless needed.
currencyNoThree-letter currency code, e.g. AUD. Only listings priced in it are returned.
in_stockNotrue = only listings seen in stock in the last 72 hours. This drops most listings; leave it out and check stock on the retailer page.
max_priceNoHighest price, in `currency` (or the country's currency). Needs currency or country. No currency conversion is done.
min_priceNoLowest price, in `currency` (or the country's currency). Useful to skip accessories.

Output Schema

NameRequiredDescriptionDefault
codeNo
noteNo
countNo
foundNofalse = nothing in this catalogue matched; not proof nobody sells it
queryNo
resultsNo
human_messageNo
retailer_searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / need
      Added value: +{
      +  "description": "Optional. What the shopper needs, in one sentence: 'quiet, fits under a 40 cm cabinet'. Not used to filter. When nothing fits, it tells exNiche exactly what is missing. No personal details.",
      +  "maxLength": 600,
      +  "type": "string"
      +}
  2. Changed18 schema fields changed
    • changedInput schema / properties / color / description
      Previous value: -"Required recorded color, e.g. black."New value: +"Colour as a store would list it, e.g. black."
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "Shopper's country as a two-letter code, e.g. AU or US. Limits results to listings priced in that country's currency.",
      +  "pattern": "^[A-Za-z]{2}$",
      +  "type": "string"
      +}
    • changedInput schema / properties / currency / description
      Previous value: -"Three-letter currency code, e.g. AUD."New value: +"Three-letter currency code, e.g. AUD. Only listings priced in it are returned."
    • addedInput schema / properties / details
      Added value: +{
      +  "default": false,
      +  "description": "true = full rows (description, every matching variant). Several times larger; leave off unless needed.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / in_stock / description
      Previous value: -"Only listings seen in stock within the last 72 hours. Most stored listings are older, so this often returns nothing: leave it off and check stock at the retailer."New value: +"true = only listings seen in stock in the last 72 hours. This drops most listings; leave it out and check stock on the retailer page."
    • changedInput schema / properties / max_price / description
      Previous value: -"Maximum recorded price. Supply currency too; no currency conversion."New value: +"Highest price, in `currency` (or the country's currency). Needs currency or country. No currency conversion is done."
    • addedInput schema / properties / min_price
      Added value: +{
      +  "description": "Lowest price, in `currency` (or the country's currency). Useful to skip accessories.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Short product category or name, e.g. keyboards, shoes or coffee. Put constraints in separate fields."New value: +"The product in 2 to 4 words, brand first if the shopper named one: 'sony headphones', 'breville espresso machine', 'running shoes'. Put budget, country, size and colour in their own fields, not here."
    • changedInput schema / properties / size / description
      Previous value: -"Required recorded size, e.g. M."New value: +"Size exactly as a store would list it, e.g. M, 8, 10.5. Only listings with that recorded size are returned, so leave it out for a wider search."
    • addedInput schema / properties / sort / description
      Added value: +"price sorts need currency or country."
    • addedOutput schema / properties / count
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / found / description
      Added value: +"false = nothing in this catalogue matched; not proof nobody sells it"
    • removedOutput schema / properties / get_key
      Removed value: -{
      -  "type": "object"
      -}
    • addedOutput schema / properties / note
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / query
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / additionalProperties
      Added value: +true
    • addedOutput schema / properties / results / items / properties
      Added value: +{
      +  "availability": {
      +    "type": "string"
      +  },
      +  "currency": {
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "last_checked": {
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "link_status": {
      +    "type": "string"
      +  },
      +  "price": {
      +    "type": [
      +      "number",
      +      "null"
      +    ]
      +  },
      +  "relevance": {
      +    "type": "number"
      +  },
      +  "store": {
      +    "type": [
      +      "string",
      +      "null"
      +    ]
      +  },
      +  "title": {
      +    "type": "string"
      +  },
      +  "url": {
      +    "type": "string"
      +  }
      +}
    • addedOutput schema / properties / retailer_search
      Added value: +{
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. Changed3 schema fields changed
    • changedInput schema / properties / in_stock / description
      Previous value: -"Filter recorded availability. Availability must be checked at retailer."New value: +"Only listings seen in stock within the last 72 hours. Most stored listings are older, so this often returns nothing: leave it off and check stock at the retailer."
    • addedOutput schema / properties / get_key
      Added value: +{
      +  "type": "object"
      +}
    • removedOutput schema / properties / upgrade_url
      Removed value: -{
      -  "type": "string"
      -}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "code": {
      +      "type": "string"
      +    },
      +    "found": {
      +      "type": "boolean"
      +    },
      +    "human_message": {
      +      "type": "string"
      +    },
      +    "results": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "upgrade_url": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "properties": {
      -    "code": {
      -      "type": "string"
      -    },
      -    "found": {
      -      "type": "boolean"
      -    },
      -    "human_message": {
      -      "type": "string"
      -    },
      -    "results": {
      -      "items": {
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    "upgrade_url": {
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  6. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare read-only/open-world/idempotent; the description adds substantial context beyond that: prices are in each listing's own currency, exclude shipping and tax, are not converted, and no API key is needed. It also discloses the return shape (ranked listings with title, store, price, availability, url, last-checked) and the fallback links.

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

Conciseness5/5

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

Dense but front-loaded: purpose and retailers first, then usage trigger, then parameter guidance, then return/price caveats, then an example. No filler sentences; each clause carries information an agent needs.

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 12-parameter search tool with an output schema, the description covers purpose, usage, parameter routing, currency/price semantics, and fallback behavior. Nothing material is missing for correct invocation.

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 already 92%, so the baseline is 3, but the description adds real guidance: put the product in `query` as 2-4 words with brand first, and route budget/country/size/colour to their own fields rather than the query. The worked example reinforces correct parameter composition.

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 and resource ('Search products for sale at big retailers and well-known brand stores'), names concrete retailers and the geographic depth (Australia/US fashion), and the scope is distinct from siblings like find_retailers or check_product_link.

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?

Gives explicit when-to-use triggers ('a shopper wants a product, a price check, or somewhere to buy it') and a fallback path ('retailer_search links to try when nothing matches'). It does not explicitly name when to prefer check_product_link or find_retailers instead, so it stops short of full alternative routing.

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