Skip to main content
Glama

轻链查券|多平台商品优惠查询

query_product_coupon

查询淘宝、天猫、京东、拼多多、抖音等主流电商平台的商品优惠券、券后底价并生成转链领券购买信息

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": {
      "content": "<content>"
    },
    "name": "query_product_coupon"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes电商商品的分享文本、商品链接或淘口令

Output Schema

NameRequiredDescriptionDefault
titleNo商品标题
messageYes查询结果提示
platformNo商品平台标识
copy_textNo购买口令或推广分享文案,可能为空,需原样使用
image_urlNo商品图片地址
has_couponYes是否有可用优惠券
promotableYes是否可生成推广购买入口;无券也可能为 true
final_priceNo预估券后价或当前参考价,单位元,并非全网最低价
coupon_amountNo优惠券金额,单位元,是否有券以 has_coupon 为准
platform_nameNo商品平台名称
promotion_urlNo推广购买链接,可能为空,需原样保留参数
original_priceNo原始参考价,单位元,可能为空,不可自行倒推
coupon_conditionNo优惠券使用条件或商品优惠说明

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose a non-obvious side effect: the tool generates 转链 (converted/affiliate links) alongside price and coupon data. However, it says nothing about authentication requirements, whether all platforms are queried at once or auto-detected, rate limits, or failure behavior for unrecognized links.

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?

One sentence, front-loaded with the verb, and every clause carries information (platforms, coupon/price data, generated link output). It is dense but not padded; a slightly awkward run-on structure with stacked noun phrases is the only minor flaw.

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?

An output schema exists, so return values need not be explained. The description covers what is queried and the platforms, but for a tool that performs link conversion and multi-platform lookups it omits how platform selection works and what happens with unsupported or malformed input, leaving moderate gaps.

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% and the single `content` parameter is documented as 分享文本、商品链接或淘口令, so the schema does the work. The description adds no additional input semantics (e.g., which format is most reliable, whether multiple links can be passed). Baseline 3 is appropriate.

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 concrete verb (查询) followed by specific resources — 商品优惠券 and 券后底价 — and also states a secondary action (生成转链领券购买信息), across named platforms (淘宝、天猫、京东、拼多多、抖音). An agent can immediately tell what the tool returns. No sibling tools exist to differentiate from, which is the only thing keeping this from a 5.

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 explicit when-to-use or when-not-to-use guidance, no prerequisites, and no alternatives named. The mention of e-commerce platforms and coupon concepts only implies the usage context — an agent must infer that this is the right call when a user shares a shopping link.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources