Skip to main content
Glama

Taobao Search

taobao_search
Read-onlyIdempotent

Search Taobao and Tmall listings through the operator's Chrome session to retrieve product prices, availability, and seller details for marketplace research.

Instructions

Search Taobao and Tmall listings, rendered in the operator's Chrome.

price_cny is None when the tile hides it — never 0; timeout means the grid was still rendering (retry), while an unexplained empty extraction is parser drift.

Full field list and error codes: guide://taobao/taobao_search.

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": "taobao_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page (1-based)
queryYesSearch text, Chinese or English, e.g. '手机' or 'headphones'

Output Schema

NameRequiredDescriptionDefault
pageNo
_metaNo
countNo
itemsNo
queryNo
statusNo
tier_usedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, openWorld=true, destructive=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: results come from a live local Chrome render, price_cny is None rather than 0 when a tile hides it, timeouts are retryable, and unexplained empty results indicate parser drift. It stops short of stating session/login requirements or rate limits.

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?

Purpose is front-loaded in one short sentence, followed by a dense but useful semantics paragraph and a single pointer to the guide. Every sentence carries information, though the null/timeout/parser-drift sentence is packed tightly and could be split for scanability.

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 a rich output schema and full annotation coverage, the definition only needs to fill behavioral gaps, and it does: field edge cases, retry semantics, and a guide reference for the full field list and error codes. Minor omissions are prerequisites (browser session, login) and pagination limits (page maxes at 100) which are not discussed.

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 'query' and 'page' are already fully documented with bounds, defaults, and examples. The description adds no meaning about either parameter, so the baseline of 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?

The first sentence gives a specific verb and resource ('Search Taobao and Tmall listings') and adds a distinctive operational detail ('rendered in the operator's Chrome'). The marketplace name itself separates it from the aliexpress_search / ozon_search / wb_search siblings, though it never explicitly routes an agent between them.

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?

There is no explicit when-to-use / when-not-to-use statement or named alternative. The closest thing is operational guidance embedded in the second paragraph ('timeout means the grid was still rendering (retry)'), which tells the agent how to react to a result rather than when to pick this tool.

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