Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

aliexpress_search

Search AliExpress products by keyword and get one page of up to 60 results with prices, ratings, links, and store details. Filter by price, free shipping, Choice, or attributes, and sort by orders or price.

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.

Input Schema

TableJSON 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-200), defaults to 1
sortNoSort order. Allowed values: best_match (default), orders, price_asc, price_desc
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. Addedv1.17.9

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses pagination (one page, up to 60 results), fields returned, sorting/filtering capabilities, locale ('anonymous US English/USD'), and a key limitation (product-detail pages unavailable). It lacks details on rate limits or authentication, but for a read-only search tool it provides strong behavioral context.

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?

The description is a single, well-structured paragraph that front-loads the core purpose and then details return fields, sorting/filtering, locale, and limitations. It is efficient, though the list of returned fields is somewhat lengthy and could be streamlined without losing value.

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?

Given the tool's complexity (8 params, no output schema), the description is nearly complete: it covers purpose, return format, filtering, locale, and limitations. A minor gap is the lack of explicit guidance on when to use this tool versus other AliExpress siblings like aliexpress_reviews, but overall it provides suffient context for an agent to invoke it correctly.

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 the schema already documents all parameters in detail. The description adds some context by mentioning sorting and filtering options and referencing the search-filters endpoint for attributes, but it does not introduce significant new meaning beyond the schema. Baseline 3 is correct.

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+resource ('Search AliExpress products') and precisely describes the return scope, explicitly noting what is and is not available (product-detail pages unavailable). This clearly distinguishes it from the sibling aliexpress_search_filters and aliexpress_reviews.

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?

Explains when to use search vs the search-filters endpoint ('list the attribute values for a keyword with the search-filters endpoint'), giving a clear alternative for one aspect. However, it does not explicitly state when NOT to use this tool (e.g., for product details which are unavailable) beyond the passing note, so a 4 is appropriate.

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