Skip to main content
Glama

NeuralVerge Business Intelligence

AliExpress product reviews

run_aliexpress_product_reviews

Get buyer reviews for an AliExpress product by ID: rating, text, and buyer details. 1 point per returned record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNoReview filter. Options: image = With images, additional = Additional feedback, local = Local reviews
productYesProduct ID or URL. e.g. 1005012791281455
currencyNoCurrency. Options: USD = USD, EUR = EUR, GBP = GBP, CAD = CAD, AUD = AUD, RUB = RUB, BRL = BRL, CLP = CLP, JPY = JPY, KRW = KRW, CHF = CHF, SEK = SEK, PLN = PLN, ILS = ILS, NOK = NOK, DKK = DKK, NZD = NZD, MXN = MXN, COP = COP, TRY = TRY, THB = THB, SGD = SGD, MYR = MYR, PHP = PHP, IDR = IDR, INR = INR, VND = VND, HKD = HKD, TWD = TWD, AED = AED, SAR = SAR, CZK = CZK, HUF = HUF, RON = RON, BGN = BGN, UAH = UAH, KZT = KZT, ARS = ARS, EGP = EGP, ZAR = ZAR, CNY = CNY, PEN = PEN
languageNoContent language. Options: ar_MA = ar_MA, de_DE = de_DE, en_US = en_US, es_ES = es_ES, fr_FR = fr_FR, in_ID = in_ID, it_IT = it_IT, iw_IL = iw_IL, ja_JP = ja_JP, ko_KR = ko_KR, nl_NL = nl_NL, pl_PL = pl_PL, pt_BR = pt_BR, ru_RU = ru_RU, th_TH = th_TH, tr_TR = tr_TR, vi_VN = vi_VN
max_itemsNoMax items (up to 250) Default: 10.
translateNoTranslate to English

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / currency / description
      Previous value: -"ISO currency code for prices, e.g. USD or EUR."New value: +"Currency. Options: USD = USD, EUR = EUR, GBP = GBP, CAD = CAD, AUD = AUD, RUB = RUB, BRL = BRL, CLP = CLP, JPY = JPY, KRW = KRW, CHF = CHF, SEK = SEK, PLN = PLN, ILS = ILS, NOK = NOK, DKK = DKK, NZD = NZD, MXN = MXN, COP = COP, TRY = TRY, THB = THB, SGD = SGD, MYR = MYR, PHP = PHP, IDR = IDR, INR = INR, VND = VND, HKD = HKD, TWD = TWD, AED = AED, SAR = SAR, CZK = CZK, HUF = HUF, RON = RON, BGN = BGN, UAH = UAH, KZT = KZT, ARS = ARS, EGP = EGP, ZAR = ZAR, CNY = CNY, PEN = PEN"
    • addedInput schema / properties / currency / enum
      Added value: +[
      +  "USD",
      +  "EUR",
      +  "GBP",
      +  "CAD",
      +  "AUD",
      +  "RUB",
      +  "BRL",
      +  "CLP",
      +  "JPY",
      +  "KRW",
      +  "CHF",
      +  "SEK",
      +  "PLN",
      +  "ILS",
      +  "NOK",
      +  "DKK",
      +  "NZD",
      +  "MXN",
      +  "COP",
      +  "TRY",
      +  "THB",
      +  "SGD",
      +  "MYR",
      +  "PHP",
      +  "IDR",
      +  "INR",
      +  "VND",
      +  "HKD",
      +  "TWD",
      +  "AED",
      +  "SAR",
      +  "CZK",
      +  "HUF",
      +  "RON",
      +  "BGN",
      +  "UAH",
      +  "KZT",
      +  "ARS",
      +  "EGP",
      +  "ZAR",
      +  "CNY",
      +  "PEN"
      +]
    • changedInput schema / properties / filter / description
      Previous value: -"Review filter: all (default), with images, with additional feedback, or local reviews."New value: +"Review filter. Options: image = With images, additional = Additional feedback, local = Local reviews"
    • changedInput schema / properties / filter / enum
      Previous value: -[
      -  "all",
      -  "image",
      -  "additional",
      -  "local"
      -]New value: +[
      +  "image",
      +  "additional",
      +  "local"
      +]
    • changedInput schema / properties / language / description
      Previous value: -"AliExpress site language, e.g. en_US."New value: +"Content language. Options: ar_MA = ar_MA, de_DE = de_DE, en_US = en_US, es_ES = es_ES, fr_FR = fr_FR, in_ID = in_ID, it_IT = it_IT, iw_IL = iw_IL, ja_JP = ja_JP, ko_KR = ko_KR, nl_NL = nl_NL, pl_PL = pl_PL, pt_BR = pt_BR, ru_RU = ru_RU, th_TH = th_TH, tr_TR = tr_TR, vi_VN = vi_VN"
    • changedInput schema / properties / max_items / description
      Previous value: -"Maximum number of reviews to return (1-250, default 10). Billed at 1 point per returned record."New value: +"Max items (up to 250) Default: 10."
    • changedInput schema / properties / product / description
      Previous value: -"AliExpress product ID or URL, e.g. 1005012791281455."New value: +"Product ID or URL. e.g. 1005012791281455"
    • changedInput schema / properties / translate / description
      Previous value: -"Translate reviews into the selected language (default true)."New value: +"Translate to English"
  2. Added

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 burden, and it usefully discloses cost behavior ('1 point per returned record') plus the shape of returned data. However it omits pagination, auth, or rate-limit behavior, leaving meaningful gaps for a paid data-retrieval call.

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?

Two tight sentences, front-loaded with purpose and free of boilerplate. Every clause carries information, though it is deliberately terse rather than rich.

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

Completeness3/5

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

No output schema and six parameters, so the description must do more; it names the returned fields and the points cost, which is helpful, but says nothing about ordering, pagination, or result volume behavior. Adequate but with clear gaps.

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 the schema already documents product, filter, currency, language, max_items, and translate. The description only echoes the product-ID usage, adding nothing beyond what the schema provides; baseline 3 is appropriate.

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 and resource ('Get buyer reviews for an AliExpress product by ID') and previews the returned fields (rating, text, buyer details). The platform name distinguishes it from the many other *_reviews siblings, though it does not explicitly name a sibling it is not.

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?

No when-to-use guidance, no exclusions, and no pointer to alternatives such as run_aliexpress_product or the search tool. The agent must infer that this is the right tool purely from the name and platform.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources