Skip to main content
Glama

NeuralVerge Business Intelligence

by ai.neuralverge.api
OverviewDiscussionsAdmin

AliExpress product

run_aliexpress_product

Get AliExpress product details by ID: title, price, images, and store. Flat 5 points per successful run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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 / 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 / product / description
      Previous value: -"AliExpress product ID or URL, e.g. 1005012791281455."New value: +"Product ID or URL. e.g. 1005012791281455"
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full behavioral burden. It usefully discloses the cost model ('Flat 5 points per successful run'), which is real value-add, but says nothing about auth, rate limits, failure modes, or whether missing products error vs. return empty.

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 waste, with the core action front-loaded and the cost note placed after. Nothing redundant or padded.

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?

With no output schema, the description helpfully names what is returned (title, price, images, store) and discloses cost. Remaining gaps (error behavior, currency/language defaults) are minor for a simple 3-param read tool.

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% and includes a worked example ('1005012791281455') plus full enum value listings, so the schema does the heavy lifting. The description adds no parameter-level detail beyond identifying that lookup is by ID.

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 AliExpress product details by ID') and enumerates the returned fields (title, price, images, store). The 'by ID' phrasing implicitly separates it from run_aliexpress_product_search, but no sibling is named explicitly.

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, prerequisites, or named alternatives. The agent must infer from the name/inline 'by ID' that this is the single-product lookup versus the search sibling.

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