Skip to main content
Glama
Sign In

Finewisdom 社媒与电商数据接口

by io.github.yy05idiot
OverviewDiscussionsAdmin

douyin_product_keyword_search

Read-onlyIdempotent

按关键词搜索抖音商城商品（数据源 EveryInfra）。单次固定返回最多 5 条（按搜索排名），暂不支持翻页；page>0 直接失败且不扣费。返回商品ID、标题、价格、月销、好评率、类目、店铺、佣金比例与搜索排名。单价¥0.3/次，仅成功调用计费，失败或空结果自动退回。

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": {
      "keyword": "<keyword>"
    },
    "name": "douyin_product_keyword_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo页码，当前仅支持 0（>0 返回失败且不扣费）
countNo兼容参数，已忽略（上游固定返回 5 条）
_tokenNo备用鉴权：fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
keywordYes关键词

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / count / description
      Previous value: -"数量（默认 20）"New value: +"兼容参数，已忽略（上游固定返回 5 条）"
    • changedInput schema / properties / page / description
      Previous value: -"页码（默认 0）"New value: +"页码，当前仅支持 0（>0 返回失败且不扣费）"
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld, but the description goes well beyond them: billing model (¥0.3 per call, success-only billing, refunds on failure or empty result) and the hard failure mode for page>0 with no charge. These are exactly the cost and failure semantics an agent needs before calling.

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?

Front-loads the tool's purpose, then result shape, then cost and failure rules in tightly packed sentences with no filler. Every clause carries either a constraint or a billing fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema present, the description enumerates the returned fields (ID, title, price, monthly sales, positive-review rate, category, shop, commission rate, rank), so an agent knows exactly what it gets. Cost, pagination limits, and failure behavior are all covered for a simple 4-parameter tool.

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%, so the baseline is 3, but the description adds meaning: it explains why count is a no-op (upstream fixed at 5) and reinforces the page>0 failure-without-charge rule for the pagination parameter. The _token fallback hint is left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (搜索) and a scoped resource (抖音商城商品), which separates it from the sibling video-oriented douyin_keyword_search and from douyin_shop_search / douyin_product_detail. An agent can tell what this returns without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operational context: fixed 5 results by search rank, no pagination, page>0 fails. It does not explicitly name which sibling to use instead when the agent wants shop-level or product-detail data, so alternatives are only implied by the resource scoping.

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

All Finewisdom 社媒与电商数据接口 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources