Search for product coupons by keyword across Taobao, JD, and Pinduoduo. Filter by platform and browse page-by-page to find applicable discounts.
搜索优惠券。
Args:
keyword: 关键词或商品 ID
platform: 平台筛选 (all / taobao / jd / pdd)
page: 页码
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| keyword | Yes | ||
| platform | No | all |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
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 full burden of behavioral disclosure. It only states that it searches coupons and lists parameters, without describing return behavior, pagination semantics, or any side effects or limitations.
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 short and front-loaded with the main purpose, followed by a compact parameter list. It is efficient, though the parameter section is formatted as a docstring-style Args block rather than prose, which is acceptable for tool descriptions.
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?
The presence of an output schema reduces the need to explain return values, and the parameter explanations are mostly adequate. However, the description lacks usage guidance and behavioral context, leaving an agent to infer when and how to invoke this tool among similar siblings.
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?
Schema description coverage is 0%, but the description compensates by explaining each parameter, including the platform enum values (all/taobao/jd/pdd) and that keyword can be a keyword or product ID. This adds real meaning beyond the raw 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 states a clear verb and resource ('搜索优惠券' / search coupons), making the core purpose understandable. However, it does not differentiate from the sibling tool search_products, which could overlap in intent.
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?
The description implies usage through its name and action, and the parameter list suggests filtering by keyword and platform. But it does not explicitly state when to prefer get_coupons over search_products or any other sibling, nor does it mention exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.