Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

aliexpress_reviews

Fetch public AliExpress product reviews and rating statistics by numeric product id, returning up to 20 records per page for market or customer sentiment research.

Instructions

Get AliExpress product reviews. Returns one page of public reviews and rating statistics for a numeric AliExpress product id. AliExpress currently returns up to 20 review records per page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-indexed review page (1-50), defaults to 1
product_idYesNumeric AliExpress product id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose that it returns public reviews plus rating statistics and that pagination yields up to 20 records per page, which is genuinely useful. However, it omits cache/rate-limit behavior and whether the page bound is enforced, so coverage is partial.

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?

Three tight sentences, front-loaded with the purpose and followed by return shape and page size. Every sentence earns its place with no filler, though the ordering could foreground the page-size constraint slightly earlier.

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?

For a two-parameter read tool with no output schema, the description covers purpose, return contents, and page size, giving the agent enough to call it correctly. The main gap is the absence of guidance on page iteration limits and alternatives.

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%, so both parameters (page, product_id) are already documented in the schema with type and 1-50 bounds. The description only echoes the product id and page-size behavior without adding syntax or format detail beyond the schema, fitting the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Get AliExpress product reviews') and names the platform, plus the required numeric product id. It does not explicitly differentiate from sibling review tools like walmart_product_reviews, but the platform-specific naming makes its scope unambiguous.

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

Usage Guidelines2/5

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

The description never states when to use this tool versus alternatives (e.g., aliexpress_search) or any precondition for obtaining a product id. Usage is only implied by the tool name, leaving the agent to infer context.

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