Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

aliexpress_search

Search AliExpress products by keyword and apply price, free-shipping, Choice, category, attribute, and sort filters to return product IDs, titles, links, images, prices, ratings, and store details.

Instructions

Search AliExpress products. Returns one page (up to 60 products) of public keyword search results with product ids, titles, links, images, prices, ratings, sold text, discount, SKU id, ship-from country, and store name when AliExpress lists them. Results can be sorted and filtered by price, free shipping, the Choice program, and product attributes; list the attribute values for a keyword with the search-filters endpoint. The search uses the anonymous US English/USD locale. Product-detail pages are currently unavailable through the supported HTTP profiles.

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": {
      "q": "<q>"
    },
    "name": "aliexpress_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesFree-text search keywords
attrNoAttribute filter <attributeId>-<valueId>, from the search-filters endpoint for the same q; comma-separate up to 5 values, one per attribute group
pageNo1-indexed result page (1-60), defaults to 1
sortNoSort order. Allowed values: best_match (default), orders, price_asc, price_desc
cat_idNoSearch within one AliExpress web category id (the number in a /category/<id>/<slug>.html URL); taxonomy ids from the categories endpoint are a different namespace and are not interchangeable
choiceNoOnly products in AliExpress's Choice program
max_priceNoMaximum price in USD (0-1000000), not below min_price
min_priceNoMinimum price in USD (0-1000000)
free_shippingNoOnly free-shipping products

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.16
    • addedInput schema / properties / cat_id
      Added value: +{
      +  "description": "Search within one AliExpress web category id (the number in a /category/<id>/<slug>.html URL); taxonomy ids from the categories endpoint are a different namespace and are not interchangeable",
      +  "type": "integer"
      +}
    • changedInput schema / properties / page / description
      Previous value: -"1-indexed result page (1-200), defaults to 1"New value: +"1-indexed result page (1-60), defaults to 1"
  2. Addedv1.17.9

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the page cap (60), the anonymous US English/USD locale, and that detail pages are unavailable. Missing only things like whether results are cached or result ordering stability, but the key behavioral constraints are surfaced.

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 the core purpose, then the return fields and constraints. Dense but every sentence carries information; the enumeration of returned fields is slightly long but justified given no output schema.

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

Completeness4/5

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

For a 9-parameter search tool with no output schema and no annotations, the description covers purpose, return contents, locale, page size, and the attribute-discovery path. Adequate, though a note on result pagination limits interacting with sort/filter could round it out.

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 schema does the heavy lifting, but the description adds value by tying the attr filter to the search-filters endpoint and framing sort/filter capabilities (price, free shipping, Choice, attributes) that correspond to parameters.

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 AliExpress products') and describes the result shape (one page, up to 60 products, listed fields) so it is clearly distinguishable from aliexpress_search_filters, aliexpress_category_products, and aliexpress_suggest.

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 explicitly tells the agent to use the search-filters endpoint to obtain attribute values for a keyword, and notes that product-detail pages aren't reachable, which routes the agent away from unavailable follow-ups. It doesn't spell out when to prefer category browsing over keyword search, but the main alternatives are covered.

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

Deploy Server

Other Tools