Skip to main content
Glama
Sign In
fetchaller

fetchaller

by Averyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

search_alibaba

Search Alibaba.com B2B products and return supplier listings with tiered pricing, MOQ, and supplier info to compare sourcing options.

Instructions

Search Alibaba.com B2B products. Returns supplier listings with tiered pricing, MOQ, and supplier info.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_alibaba"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed, default: 1)
sortNoSort order: default (relevance), orders (most sold in 180 days). Alibaba has no price sort, so price_asc/price_desc re-order the returned page by lowest listed price and say sodefault
queryYesSearch query
timeoutNoEnd-to-end timeout in seconds (default: 180)
max_priceNoMaximum price filter, in the currency results are priced in
min_priceNoMinimum price filter, in the currency results are priced in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv3.8.11
    • changedInput schema / properties / max_price / description
      Previous value: -"Maximum price filter (USD)"New value: +"Maximum price filter, in the currency results are priced in"
    • changedInput schema / properties / min_price / description
      Previous value: -"Minimum price filter (USD)"New value: +"Minimum price filter, in the currency results are priced in"
    • changedInput schema / properties / sort / description
      Previous value: -"Sort order"New value: +"Sort order: default (relevance), orders (most sold in 180 days). Alibaba has no price sort, so price_asc/price_desc re-order the returned page by lowest listed price and say so"
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "default",
-  "price_asc",
-  "price_desc"
-]New value: +[
+  "default",
+  "orders",
+  "price_asc",
+  "price_desc"
+]
  2. First observedv3.3.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the shape of results (supplier listings with tiered pricing, MOQ, supplier info), which is useful, but says nothing about authentication, rate limits, pagination behavior, or that results may be empty for niche queries. For a read-only search this is adequate but thin.

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 sentences, zero filler, with the verb and resource front-loaded and the return contents immediately following. Nothing in it is redundant with the title or schema.

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?

With six parameters, no annotations, and no output schema, the description should do more: it never explains the pagination ceiling, result-count behavior, or how the price filters interact with the currency caveat in the schema. The one-line return summary is the only compensation offered for the missing output schema.

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%, with the sort enum, page bounds, and price filters all documented in-schema, including the caveat that Alibaba has no native price sort. The description adds no parameter meaning beyond that, so baseline 3 applies.

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 ("Search Alibaba.com B2B products") and previews the return payload (supplier listings, tiered pricing, MOQ). It does not name its natural sibling get_alibaba_product or distinguish itself from search_aliexpress/search_marketplace, so an agent must infer the boundary from the domain name alone.

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?

There is no when-to-use or when-not-to-use guidance. The description never mentions that get_alibaba_product should be used once a listing is identified, nor does it contrast with search_aliexpress for retail vs. B2B sourcing. Usage is only implied by the word "Search".

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