Skip to main content
Glama

NeuralVerge Business Intelligence

by ai.neuralverge.api
OverviewDiscussionsAdmin

AliExpress product search

run_aliexpress_product_search

Search AliExpress products by keyword: title, price, and image. 1 point per returned record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort by. Options: orders = Orders, price_low_to_high = Price: low to high, price_high_to_low = Price: high to low
choiceNoAliExpress Choice
countryNoShip-to country. e.g. US
filtersNoAttribute filters. e.g. Comma-separated
keywordYesSearch term. e.g. wireless mouse
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: 25.
max_priceNoMax price
min_priceNoMin price
ship_fromNoShip-from country. e.g. Any
start_pageNoStarting page Default: 1.
free_shippingNoFree shipping
local_shippingNoLocal shipping
four_star_and_upNo4 stars & up

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changed
    • changedInput schema / properties / choice / description
      Previous value: -"Only AliExpress Choice items."New value: +"AliExpress Choice"
    • changedInput schema / properties / country / description
      Previous value: -"Ship-to country, ISO 3166 alpha-2 code, e.g. US."New value: +"Ship-to country. e.g. US"
    • removedInput schema / properties / country / maxLength
      Removed value: -2
    • removedInput schema / properties / country / minLength
      Removed value: -2
    • 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"
+]
    • addedInput schema / properties / filters
      Added value: +{
+  "description": "Attribute filters. e.g. Comma-separated",
+  "type": "string"
+}
    • changedInput schema / properties / four_star_and_up / description
      Previous value: -"Only items rated 4 stars and up."New value: +"4 stars & up"
    • changedInput schema / properties / free_shipping / description
      Previous value: -"Only items with free shipping."New value: +"Free shipping"
    • changedInput schema / properties / keyword / description
      Previous value: -"Search term, e.g. 'wireless mouse'."New value: +"Search term. e.g. wireless mouse"
    • 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 / local_shipping / description
      Previous value: -"Only items shipped from a local warehouse."New value: +"Local shipping"
    • changedInput schema / properties / max_items / description
      Previous value: -"Maximum number of products to return (1-250, default 25). Billed at 1 point per returned record."New value: +"Max items (up to 250) Default: 25."
    • changedInput schema / properties / max_price / description
      Previous value: -"Maximum price."New value: +"Max price"
    • removedInput schema / properties / max_price / minimum
      Removed value: -0
    • changedInput schema / properties / min_price / description
      Previous value: -"Minimum price."New value: +"Min price"
    • removedInput schema / properties / min_price / minimum
      Removed value: -0
    • changedInput schema / properties / ship_from / description
      Previous value: -"Ship-from country, ISO 3166 alpha-2 code, e.g. CN."New value: +"Ship-from country. e.g. Any"
    • removedInput schema / properties / ship_from / maxLength
      Removed value: -2
    • removedInput schema / properties / ship_from / minLength
      Removed value: -2
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order (default best_match)."New value: +"Sort by. Options: orders = Orders, price_low_to_high = Price: low to high, price_high_to_low = Price: high to low"
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "best_match",
-  "orders",
-  "price_low_to_high",
-  "price_high_to_low"
-]New value: +[
+  "orders",
+  "price_low_to_high",
+  "price_high_to_low"
+]
    • changedInput schema / properties / start_page / description
      Previous value: -"Result page to start from (default 1)."New value: +"Starting page Default: 1."
  2. Added

TDQS

A3.5/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. It usefully discloses the cost model ('1 point per returned record'), which is real behavioral context an agent should weigh. However, it omits pagination behavior (start_page/max_items are undocumented in the description) and any rate-limit or return-shape caveats.

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?

Two short sentences, zero filler, with the core purpose front-loaded before the cost note. Everything stated earns its place.

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?

For a 15-parameter search tool with no annotations and no output schema, the description is thin: it briefly names return fields but gives no pagination, result-volume, or filtering guidance. Cost is covered, but an agent would need the schema to fully operate it.

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 all 15 parameters are already documented in the schema (enums, defaults, min/max). The description adds no parameter-level detail beyond the schema, which is the expected baseline for a fully documented schema.

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 (Search) and resource (AliExpress products) with the key input dimension (by keyword) and a brief hint at returned fields. It is clearly distinguishable from run_aliexpress_product_reviews, though it does not explicitly differentiate itself from the sibling run_aliexpress_product (detail lookup).

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 phrase 'by keyword' implies the tool is for keyword-driven discovery, but there is no explicit when-to-use guidance, no statement of when to prefer run_aliexpress_product instead, and no mention of prerequisites or limitations. Usage is only inferable.

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

All NeuralVerge Business Intelligence toolsInspect
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