Crawlora MCP

aliexpress_suggest

Read-only

AliExpress's own search-box keyword completions for a query: each suggestion is a keyword plus the matching AliExpress search URL. q is a partial or full query, e.g. wireless earbuds; limit caps the result (1-20, default 10) and AliExpress usually offers 10-12. This is autocomplete, not a product list -- pass a suggestion's keyword to aliexpress_search to get products, and do not expect prices or ids here. A query AliExpress has no completion for returns an empty suggestions list rather than an error.

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_suggest"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Required. Partial or full search keywords to complete, e.g. 'wireless earbuds'.
`limit`	No	Optional. Maximum number of suggestions to return (1 to 20), defaults to 10. AliExpress usually returns 10-12.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

readOnlyHint and openWorldHint already cover the safety profile, so the bar is lower. Beyond that, the description adds the empty-list-rather-than-error behavior and the typical 10-12 result count, which are genuinely useful traits not present in annotations. It stops short of deep detail, so a 4 rather than 5.

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 alternatives and edge cases follow in a tight sequence. Dense but every sentence carries signal; only the trailing empty-list note borders on extra but it clarifies behavior.

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?

An output schema exists, so return values are already structured; the description still clarifies the autocomplete nature and edge cases. For a 2-param read tool this is effectively complete, with no meaningful gaps left for an agent.

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 already documents both params and defaults. The description adds marginal meaning with 'AliExpress usually offers 10-12' completions, informing practical use of limit, which goes slightly beyond the schema's stated range.

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 ('keyword completions for a query') and immediately clarifies the output shape (keyword + matching search URL). It distinguishes itself from aliexpress_search by explicitly saying 'this is autocomplete, not a product list', so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Explicitly instructs passing a suggestion's keyword to aliexpress_search to get products, establishes what not to expect (prices, ids), and notes the empty-list edge case. Both the when-to-use and the alternative are named.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?