Skip to main content
Glama

Taobao Item Card

taobao_card
Read-onlyIdempotent

Fetches a Taobao item card by item ID or item.taobao.com URL, returning price, availability, and variant details; price is null when hidden or variant-based.

Instructions

Fetch one Taobao item card.

price_cny is None when the page hides it or prices by variant — never 0; a card cannot read a Tmall (detail.tmall.com) listing, so use the search row for it.

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

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": {
      "item_id_or_url": "<item_id_or_url>"
    },
    "name": "taobao_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_id_or_urlYesItem id or item.taobao.com URL

Output Schema

NameRequiredDescriptionDefault
urlNo
_metaNo
salesNo
titleNo
statusNo
item_idNo
price_cnyNo
shop_nameNo
tier_usedNo
description_imagesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds useful behavioral context beyond annotations: price_cny is None rather than 0 when hidden or variant-priced, and Tmall listings cannot be read.

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?

The description is short, front-loaded, and every sentence adds operational value: purpose, price edge case, Tmall limitation, and guide reference. There is no wasted wording.

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?

For a one-parameter read-only card tool with an output schema and rich annotations, this is largely complete. It covers key caveats and points to the guide for full fields and error codes, though it remains somewhat dependent on that external reference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is already documented as an item id or item.taobao.com URL. The description still adds acceptance meaning by stating that detail.tmall.com listings cannot be read, which directly affects what URL should be passed.

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 description uses a specific verb and resource: 'Fetch one Taobao item card.' It also limits scope by noting Tmall listings cannot be read. However, the sibling alternative is referred to only as 'the search row' rather than named explicitly, so differentiation is clear but not maximally precise.

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 description provides one routing rule: use search for Tmall detail.tmall.com listings. It does not broadly explain when to choose this card tool versus taobao_search for normal Taobao browsing or lookup.

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