SiteCheck Shop & Social

AliExpress product search from the public search page

ecommerce_aliexpress

Read-only

AliExpress product search from the public search page: product ID, title, sale price and original price with currency code, discount %, promo label (welcome-gift cards have no price), star rating and units-sold text when shown, listing date, image and product URL; 60 products per page plus the total result count. Language and currency can follow the caller's region (the currency code is always returned). Unofficial page data, may change. Usually answers in a few seconds, up to 17 s on slower calls; allow a 30 s timeout. Related tools on this server, for a different need: ecommerce_petco when you need Petco.com product search read from the public search page; ecommerce_zazzle when you need Zazzle product search from the public search page: product. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "ecommerce_aliexpress"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search words, e.g. phone case, air fryer (required, 2-80 chars)
`page`	No	Page number 1 to 60 (default 1)

Output Schema

Name	Required	Description	Default
`q`	No
`page`	No
`count`	No
`total`	No
`source`	No
`products`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare read-only and open-world, and the description adds substantial context beyond them: 60 products per page plus a total count, currency code always returned, promo/welcome-gift cards may lack a price, data is scraped from an unofficial page and may change, and it names the exact cost model ($0.002 USDC via x402, failed calls not charged). That is exactly the behavioral disclosure an agent needs before calling a paid, scraper-backed tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and every operational detail (caveats, latency, price) earns its place, but the return-field list is delivered as one long semicolon-chained sentence that is hard to scan. The trailing sibling block also restates "public search page" phrasing for other sites, which adds length without much decision value.

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

Completeness5/5

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

Pagination size, total counts, latency limits, pricing, and data-stability caveats are all covered, and an output schema exists so return values need no further explanation. Nothing an agent needs in order to call this correctly is missing.

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 q and page are already documented, and the baseline would be 3. The description still adds meaning the schema lacks: results are returned 60 at a time with a total count, and language/currency can follow the caller's region — both of which change how an agent sets and interprets the page parameter.

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?

"AliExpress product search from the public search page" gives a specific verb and resource, and the description then enumerates exactly what comes back (product ID, title, sale/original price with currency, discount %, promo label, rating, units sold, listing date, image, URL). An agent immediately knows this is AliExpress search rather than Amazon, Lazada, or Trendyol search.

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 names two concrete alternatives (ecommerce_petco, ecommerce_zazzle) and the condition that selects them, and adds operational guidance that shapes invocation: allow a 30 s timeout, expect a few seconds normally. What's missing is when NOT to use it — e.g., whether another AliExpress-specific or cross-marketplace search sibling should be preferred — so it is clear context without exclusions.

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

All SiteCheck Shop & Social 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?