Skip to main content
Glama

AliExpress Search

aliexpress_search
Read-onlyIdempotent

Search AliExpress for products and retrieve structured data including prices, availability, ratings, and seller details. Results include price in RUB or null when absent.

Instructions

Search AliExpress, rendered in the operator's Chrome.

Return Format

AliSearchResponse: {status, query, tier_used, count, items[], meta}. price_rub is None when absent — never 0.

Error Format

ToolError: TransportDownError on x5sec challenges or CDP failures (with the manual-check hint inline); ParserDriftError when a rendered page yields zero product tiles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch text, e.g. 'умные часы'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_metaNo
countNo
itemsNo
queryNo
statusNo
tier_usedNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv1.6.0

TDQS

A4/5.0
Behavior4/5

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

The description goes beyond the readOnly annotation by specifying return format (AliSearchResponse) and error conditions (TransportDownError, ParserDriftError), adding useful operational context.

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 concise, front-loaded with the main purpose, and well-structured with clear sections for return and error formats.

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?

The description covers return and error formats adequately for a simple search tool, though it does not elaborate on the 'rendered in the operator's Chrome' context or any additional configuration.

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 describes the 'query' parameter with an example, and the tool description does not add extra semantic details about it.

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 clearly states that the tool searches AliExpress, which distinguishes it from other marketplace search tools in the sibling list.

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

Usage Guidelines3/5

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

The description does not explicitly mention when to use this tool versus alternatives, but the name and context imply it is for AliExpress searches. Lacks explicit guidance on choice.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Vladimir-Human/ru-marketplace-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server