Skip to main content
Glama

SocialDataX 抖音 Douyin MCP

by com.52choujiang
OverviewDiscussionsAdmin

douyin_search_users

Read-only

搜索抖音用户、账号、博主、创作者或达人，支持 page_token 翻页。用户需要按搜索词查找用户时使用；已有 sec_user_id 或用户主页链接时使用相应用户资料或列表工具；不用于搜索作品。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes搜索词，可传昵称、抖音号、账号名、达人名称或创作者/博主名称；不用于搜索作品；不要传作品链接、用户主页链接、sec_user_id 或 page_token。
user_typeNo用户类型筛选，可选：all（不限，默认）、regular_user（普通用户）、enterprise_verified（企业认证）、individual_verified（个人认证）。如无明确筛选需求，保持 all。all
page_tokenNopage_token 是不透明分页令牌。首次请求留空；继续翻页时必须将上一次返回的完整 next_page_token 原样传入，作为 page_token 使用；只能用于同一搜索链路，不能跨能力、关键词或筛选条件复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。
follower_count_rangeNo用户粉丝数量筛选，可选：all（不限，默认）、under_1k（1000 以下）、1k_to_10k（1000-1 万）、10k_to_100k（1 万-10 万）、100k_to_1m（10 万-100 万）、over_1m（100 万以上）。如无明确筛选需求，保持 all。all

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes当前页用户搜索结果列表
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
next_page_tokenYes下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回。next_page_token 只能用于同一能力和同一分页链路，不能跨能力、作品、用户、评论、关键词或筛选条件复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / items / items / properties / sec_user_id / description
      Previous value: -"用户 sec_user_id；用户主页和作品工具可直接复用"New value: +"用户 sec_user_id；当前不可用时为空字符串"
  2. Changed1 schema field changed
    • changedInput schema / properties / keyword / description
      Previous value: -"抖音用户、账号、博主、创作者或达人搜索自然语言关键词；可传昵称、抖音号、账号名或达人名称；不用于搜索作品；不要传作品链接、用户主页链接、sec_user_id 或 page_token 作为 keyword。"New value: +"搜索词，可传昵称、抖音号、账号名、达人名称或创作者/博主名称；不用于搜索作品；不要传作品链接、用户主页链接、sec_user_id 或 page_token。"
  3. Changed2 schema fields changed
    • addedOutput schema / properties / points
      Added value: +{
+  "additionalProperties": false,
+  "description": "本次成功调用的积分消耗与调用完成时的账户积分余额。",
+  "properties": {
+    "balance": {
+      "description": "本次接口完成时看到的当前积分余额。",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "cost": {
+      "description": "本次请求最终确认消耗的积分。",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "cost",
+    "balance"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "items",
-  "next_page_token"
-]New value: +[
+  "items",
+  "next_page_token",
+  "points"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / keyword / description
      Previous value: -"抖音用户、账号、博主、创作者或达人搜索关键词；可传昵称、抖音号、账号名或达人名称；不用于搜索作品。"New value: +"抖音用户、账号、博主、创作者或达人搜索自然语言关键词；可传昵称、抖音号、账号名或达人名称；不用于搜索作品；不要传作品链接、用户主页链接、sec_user_id 或 page_token 作为 keyword。"
  5. Changed9 schema fields changed
    • changedInput schema / properties / follower_count_range / default
      Previous value: -""New value: +"all"
    • changedInput schema / properties / follower_count_range / description
      Previous value: -"用户粉丝数量筛选，可选：空字符串（不限，默认）、0_1k（1000以下）、1k_1w（1000-1w）、1w_10w（1w-10w）、10w_100w（10w-100w）、100w_（100w以上）。如无明确筛选需求，保持空字符串。"New value: +"用户粉丝数量筛选，可选：all（不限，默认）、under_1k（1000 以下）、1k_to_10k（1000-1 万）、10k_to_100k（1 万-10 万）、100k_to_1m（10 万-100 万）、over_1m（100 万以上）。如无明确筛选需求，保持 all。"
    • changedInput schema / properties / follower_count_range / enum
      Previous value: -[
-  "",
-  "0_1k",
-  "1k_1w",
-  "1w_10w",
-  "10w_100w",
-  "100w_"
-]New value: +[
+  "all",
+  "under_1k",
+  "1k_to_10k",
+  "10k_to_100k",
+  "100k_to_1m",
+  "over_1m"
+]
    • changedInput schema / properties / keyword / description
      Previous value: -"抖音用户搜索关键词"New value: +"抖音用户、账号、博主、创作者或达人搜索关键词；可传昵称、抖音号、账号名或达人名称；不用于搜索作品。"
    • changedInput schema / properties / user_type / default
      Previous value: -""New value: +"all"
    • changedInput schema / properties / user_type / description
      Previous value: -"用户类型筛选，可选：空字符串（不限，默认）、common_user（普通用户）、enterprise_user（企业认证）、personal_user（个人认证）。如无明确筛选需求，保持空字符串。"New value: +"用户类型筛选，可选：all（不限，默认）、regular_user（普通用户）、enterprise_verified（企业认证）、individual_verified（个人认证）。如无明确筛选需求，保持 all。"
    • changedInput schema / properties / user_type / enum
      Previous value: -[
-  "",
-  "common_user",
-  "enterprise_user",
-  "personal_user"
-]New value: +[
+  "all",
+  "regular_user",
+  "enterprise_verified",
+  "individual_verified"
+]
    • addedOutput schema / properties / items / items / properties / posted_content_count
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "用户已发布作品数量，包含视频、图文等作品；当前不可用时为 null"
+}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
-  "user_id",
-  "sec_user_id",
-  "name",
-  "avatar_url",
-  "profile_url",
-  "bio",
-  "verification_label",
-  "verified",
-  "follower_count",
-  "following_count",
-  "received_like_count",
-  "douyin_id"
-]New value: +[
+  "user_id",
+  "sec_user_id",
+  "name",
+  "avatar_url",
+  "profile_url",
+  "bio",
+  "verification_label",
+  "verified",
+  "follower_count",
+  "following_count",
+  "received_like_count",
+  "douyin_id",
+  "posted_content_count"
+]
  6. Added

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already communicate readOnly and openWorld behavior, and the description adds further behavioral context by noting pagination support ('支持 page_token 翻页') and by clarifying the tool is keyword-driven rather than identity- or media-driven. It does not explain search semantics beyond pagination, but with readOnlyHint and openWorldHint already available, the added context is sufficient.

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?

The description is compact, front-loads the core action and resource, then gives routing guidance and exclusions. Every sentence adds distinct value with no filler, and the length is appropriate for the tool's complexity.

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?

Given the 100% schema coverage, rich parameter descriptions, output schema, and readOnly/openWorld annotations, the description provides just enough extra context: it confirms pagination and clearly distinguishes when to use this tool versus sibling tools. No necessary guidance appears missing.

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%, so the input schema already documents every parameter in detail. The description mentions pagination and search terms but adds no parameter semantics beyond what the schema already provides, so the baseline 3 applies.

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?

The description uses a specific action and resource, '搜索抖音用户、账号、博主、创作者或达人', and explicitly separates this from sibling tools by stating it is not for searching works. It also routes users with an existing sec_user_id or profile link to the corresponding profile/list tools, making differentiation clear.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('用户需要按搜索词查找用户时使用') and when not to use it, including both having an identity identifier/link and searching for works. It also points to the alternative category '相应用户资料或列表工具', providing actionable routing without relying on inference.

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

All SocialDataX 抖音 Douyin MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources