Skip to main content
Glama
Sign In

Finewisdom 社媒与电商数据接口

by io.github.yy05idiot
OverviewDiscussionsAdmin

douyin_keyword_search

Read-onlyIdempotent

按关键词搜索抖音内容（综合搜索，返回视频列表）。每页约25条，单次实际返回23~24条；page>0时服务端自动预热首页获取search_id完成翻页链（预热不计费）；触发风控或无结果时返回code:false且不扣费，应按失败处理而非空数据。返回字段:aweme_id,desc,author,like/comment/share/collect,publish_time,_search_id/_page/_next_offset。返回视频列表，含每条内容ID与基础互动数据。做关键词监测、内容发现或构建候选集时用，ID可继续调详情与评论接口。单价¥0.1/次，仅成功调用计费，失败或空结果自动退回。

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_keyword_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo页码，内部 offset=page*25（默认 0，范围 0~40）
_tokenNo备用鉴权：fw_ 开头的 token。推荐改用 HTTP Header X-FW-Token。
keywordYes关键词

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, but the description adds far more: ¥0.1 per call billed only on success, automatic refund on failure or empty results, server-side warm-up of page 0 to obtain search_id (not billed), and the critical warning that code:false on risk control means failure rather than empty data. This is exactly the operational context an agent needs and cannot get from annotations.

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?

Purpose is front-loaded and the sentences about billing, pagination and failure semantics all carry weight. The return-field enumeration is somewhat dense and run-on, but it is necessary given there is no output schema.

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, the description compensates by listing returned fields (aweme_id, desc, author, interactions, publish_time, _search_id/_page/_next_offset) and explaining pagination continuation via _next_offset. Billing, failure classification and downstream chaining are all covered, leaving nothing an agent needs to call it correctly.

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 baseline is 3, but the description adds real meaning: effective page size is 23–24 despite ~25 nominal, and page>0 triggers a warm-up request that acquires search_id for the pagination chain. The _token parameter is left to the schema, so not a full 5.

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+resource (按关键词搜索抖音内容) and scopes it as 综合搜索 returning a video list, which cleanly separates it from detail/comment tools. The follow-on note that returned IDs feed 详情与评论接口 further pins its role in the tool graph.

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?

Explicitly names the use cases (关键词监测、内容发现、构建候选集) and the chaining path to detail/comment endpoints. It stops short of naming when NOT to use it or contrasting with adjacent search siblings (e.g. product/shop search), so it stops at 4.

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