AliExpress MCP

Overview Schema Source Related Servers Discussions Admin

Get Aliexpress Product

get_aliexpress_product

Fetch a single AliExpress product's full record: price, rating, specs, stock, shipping, and images. Returns complete data or a partial fallback with reasons when anti-bot limits access.

Instructions

Retrieve the record of one AliExpress product.

Use after search_aliexpress surfaces something worth a closer look.

How complete the answer is depends on which source could serve it, so check the source and partial fields before describing it to the user:

source: "mtop", partial: false — the full record: title, selected-variant price plus per-variant pricing, star rating and review count, orders sold, stock, the store (name, positive rating, country), shipping (origin, ship-to, delivery estimate), the SKU option axes (e.g. colour / size), specifications and all product images.
source: "ssr+search", partial: true — AliExpress is currently gating its detail API behind an anti-bot challenge, so the record is composed from the product page and search results: title, images, url, price, rating and orders. Every field that could not be obtained is named in unavailable. Occasionally even price/rating cannot be recovered; price_note explains why and search_status distinguishes the two causes — blocked (AliExpress is rate-limiting right now, so it is worth retrying later) from not_found (the listing genuinely did not turn up in search). Say which one it was rather than just "no price available".

Prices are in the configured currency (EUR by default). A field listed in unavailable is unknown, not absent from the listing — do not tell the user a product has no variants, no reviews or no shipping options on that basis; say that detail could not be retrieved.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`product`	Yes	AliExpress product id (a numeric string such as '1005009258005772') or a full product URL like 'https://www.aliexpress.com/item/1005009258005772.html'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.2Sep 17, 2026

TDQS

A4.7/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 of behavioral disclosure. It thoroughly explains that the response can be full (`source: "mtop"`) or partial (`source: "ssr+search"`), describes the anti-bot gating, and clarifies how to interpret `unavailable`, `price_note`, and `search_status` (including the `blocked` vs `not_found` distinction). It also notes the currency configuration. This goes far beyond a generic read-only hint and gives the agent actionable knowledge about edge cases.

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

Conciseness5/5

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

The description is longer than average, but it is well-structured and front-loaded. The core purpose and usage trigger are in the first two sentences, followed by a bulleted breakdown of response sources and interpretive guidance. Each sentence earns its place – there is no redundancy or filler, and the formatting makes the conditional logic easy to parse.

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?

Given the tool's complexity and the presence of an output schema, the description is exceptionally complete. It covers the two possible response shapes, how to distinguish unknown fields from truly absent ones, how to handle price retrieval failures, and even how to communicate results to the user. The agent has everything it needs to invoke the tool and interpret the response 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?

The input schema already provides a complete description of the `product` parameter, covering both numeric ID and full URL formats. The tool description adds no additional meaning about the parameter itself – it only restates that it retrieves "one AliExpress product." With 100% schema coverage, baseline 3 is appropriate.

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 description opens with a specific verb and resource: "Retrieve the record of one AliExpress product." It also positions itself relative to the sibling by stating "Use after `search_aliexpress` surfaces something worth a closer look," which clearly distinguishes this detail-lookup tool from the search tool.

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?

The description explicitly states when to use the tool: "Use after `search_aliexpress` surfaces something worth a closer look." This names the sibling and gives an explicit trigger condition, leaving no ambiguity about workflow ordering. It also instructs the agent to check `source` and `partial` fields before describing the result, which is practical guidance for correct use.

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

Deploy Server