Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

aliexpress_trending_searches

Fetch AliExpress trending search keywords by category, including hot, discovery, and shading terms with labels and search URLs for keyword research.

Instructions

List AliExpress trending searches. Returns AliExpress's own discovery/trending keyword feed from its anonymous search box: the hot-search keywords it groups by category, plus its discovery and shading keyword modules. Each item carries the keyword, its display casing when different, the kind (hot, shading, discovery, history), the module's UI label, the hot-list category, and a ready-to-use search URL; keyword thumbnails are included where AliExpress supplies them. This is a keyword-discovery feed, not a product list and not a personalized recommendation: no product id, title, price or seller is returned, and AliExpress does not promise a stable order between calls. The anonymous feed carries roughly 40 hot keywords plus a few discovery/shading keywords per call; search history is empty for anonymous callers.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum trending keywords to return (1-20), defaults to 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well: it states that callers are anonymous, that the feed carries roughly 40 hot keywords plus a few discovery/shading keywords, that ordering is not guaranteed stable between calls, and that search history is empty for anonymous callers. It also details what each item contains (keyword, display casing, kind, module label, category, search URL, thumbnails).

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 core statement is front-loaded and every clause is informative, listing return fields and the anonymous-feed caveats. It is somewhat long and the 'not a product list and not a personalized recommendation' claim is partially restated by the 'no product id, title, price or seller' clause, so a small amount of redundancy keeps it from a 5.

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?

There is no output schema, but the description compensates by enumerating the item fields and the module structure an agent will receive. What's missing is how the 'limit' interacts with the per-module feed (whether it truncates the hot list, drops modules, or both) and any error behavior for out-of-range values, leaving a small gap for a tool with no output schema.

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 100% and the single 'limit' parameter (1-20, default 10) is fully documented in the schema. The description adds no syntax or behavioral detail about the limit, such as whether it truncates across modules or how it interacts with the ~40-keyword feed, so the baseline of 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?

The first sentence gives a specific verb+resource ('List AliExpress trending searches') and the following sentences delimit the exact scope: a keyword-discovery feed drawn from the anonymous search box, with hot/shading/discovery/history modules. It explicitly distinguishes the result from a product list and a personalized recommendation, so an agent knows what it will and won't get.

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 gives clear positive context (keyword discovery from AliExpress's own trending feed) and clear negative exclusions (not a product list, not personalized recommendations), which effectively routes an agent away from product search tools. However, it never names a concrete alternative sibling such as aliexpress_suggest or aliexpress_search, so the when-to-use-this-instead-of-that decision is left to inference.

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