Skip to main content
Glama

Search products

search_products
Read-onlyIdempotent

Search AliExpress for products, prices and alternatives. Returned links are affiliate links.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results.
queryYesOriginal product request, in any language; used to check relevance.
countryNoDelivery country (ISO 3166-1 alpha-2). Default: client location, else DE.
sort_byNorelevance
currencyNoPrice currency. Default follows the delivery country.
max_priceNoHighest price in the selected currency.
min_priceNoLowest price in the selected currency.
search_termsYes3–10 different English search phrases (2–5 words) for the same product: common name, synonyms, seller terms. Keep essential specifications. More phrases find more.
required_title_termsNoLiteral words required in each title or variant options; put semantic requirements in query.

Output Schema

NameRequiredDescriptionDefault
hintNoSuggested next step when the search is incomplete.
itemsYes
statusNo
countryYesDelivery country for these prices; keep it for get_product_details.
currencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a genuinely non-obvious behavioral fact the annotations cannot express: returned links are affiliate links, which matters for how an agent presents results. It still omits rate limits and result-count/pagination behavior, keeping it below 5.

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?

Two short sentences with zero filler; the core action is front-loaded and the affiliate disclosure is a compact second sentence. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, rich annotations and near-complete parameter documentation, most burden is carried elsewhere, so the description need not explain return values. However, for a 9-parameter tool with two siblings it is thin: it gives no positioning relative to get_product_details/show_pictures and no guidance on the heavy search_terms/query distinction.

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 description coverage is 89%, so the schema already explains query, search_terms, country, currency, price bounds and required_title_terms in detail. The description adds no parameter meaning beyond naming 'prices', so the baseline of 3 applies.

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?

States a specific verb and resource ('Search AliExpress for products, prices and alternatives'), which is far more informative than the title 'Search products'. It does not explicitly differentiate from siblings get_product_details or show_pictures, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no statement of when not to use it, and no routing to get_product_details or show_pictures. The only hint is the word 'alternatives', which is never explained, leaving the agent to infer that this is the discovery entry point.

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