Retrieve detailed product information and available coupons for a specific product across Taobao, JD, or PDD platforms. Use it to obtain accurate product data and discount details for price comparison.
获取单品详情 (含优惠券信息)。
Args:
product_id: 平台侧商品 ID
platform: 平台 (taobao / jd / pdd)
| Name | Required | Description | Default |
|---|---|---|---|
| platform | Yes | ||
| product_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It communicates a read-oriented retrieval and a notable output trait ('含优惠券信息'), but it does not explicitly state read-only behavior, platform-specific return differences, authorization needs, or error behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded: one clear purpose line followed by two parameter lines. Every element earns its place and there is no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter detail lookup, the description plus the provided output schema covers the core invocation requirements: required parameters, platform values, and the inclusion of coupon data. The main missing piece is usage guidance, but the operational context an agent needs to call the tool is present.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the Args section compensates meaningfully: it defines product_id as the platform-side product ID and spells out the platform values (taobao / jd / pdd). This adds real semantics beyond the bare parameter names in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource ('获取单品详情', getting single-item details) and adds that coupon information is included. This clearly indicates the tool retrieves one product's full detail rather than searching or comparing, distinguishing it from siblings like search_products and compare_prices.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance about when to use this tool versus the sibling tools. The existence of get_coupons, search_products, compare_prices, and parse_and_compare suggests a detail lookup, but the description does not state when to prefer get_product_detail over those alternatives or mention any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.