SocialDataX TikTok MCP

tiktok_search_users

Read-only

按非空搜索词搜索 TikTok 用户，用于按用户名、昵称或品牌名查找候选用户，返回公开用户资料并支持 page_token 翻页；搜索结果不提供 private_account、following_count 和 posted_content_count，省略这些字段；是否继续翻页仅以 next_page_token 是否为空为准。返回用户搜索结果 items；非空的 items[].tiktok_id 可直接传给用户资料和用户作品工具；非空的 items[].profile_url 可直接传给用户资料和用户作品工具；仅使用非空标识调用对应入口。已知准确用户标识且只需上述后续数据时，使用对应入口，无需先搜索。

Input Schema

Name	Required	Description	Default
`keyword`	Yes	keyword 为非空搜索词，可传用户名、账号名、昵称、品牌名或机构名，例如 teamtrump、campinglife；不要传用户主页链接、作品链接、用户数字 ID、post_id 或分页令牌 page_token。
`page_token`	No	请求分页令牌是不透明令牌。请求的 page_token 为空字符串表示首页；继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。

Output Schema

Name	Required	Description
`items`	Yes	当前页 TikTok 用户搜索结果；没有匹配用户时为空数组；是否继续翻页仅以 next_page_token 是否为空为准
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`next_page_token`	Yes	用户搜索响应分页令牌是不透明令牌。响应的 next_page_token 为空字符串表示没有更多结果；非空时必须将完整令牌原样作为下一次请求的 page_token 传回；不能修改、截断、脱敏、格式化、重组，也不能跨关键词或不同请求链路复用。

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 8, 2026

addedOutput schema / properties / items / items / properties / follower_count / default
```
Added value: +null
```

changedOutput schema / properties / items / items / properties / follower_count / description

Previous value: -"粉丝数；当前不可用时为 null"New value: +"粉丝数；未知时省略"

addedOutput schema / properties / items / items / properties / following_count / default
```
Added value: +null
```

changedOutput schema / properties / items / items / properties / following_count / description

Previous value: -"关注数；用户搜索当前不提供，固定为 null"New value: +"关注数；用户搜索当前不提供，省略该字段"

addedOutput schema / properties / items / items / properties / posted_content_count / default
```
Added value: +null
```

changedOutput schema / properties / items / items / properties / posted_content_count / description

Previous value: -"用户已发布作品数；用户搜索当前不提供，固定为 null"New value: +"用户已发布作品数；用户搜索当前不提供，省略该字段"

addedOutput schema / properties / items / items / properties / private_account / default
```
Added value: +null
```

changedOutput schema / properties / items / items / properties / private_account / description

Previous value: -"用户账号是否为私密账号；true 表示私密，false 表示非私密，null 表示未知；当前用户搜索不提供隐私状态，返回 null，不可据此判断账号是否公开"New value: +"用户账号是否为私密账号；true 表示私密，false 表示非私密；当前用户搜索不提供隐私状态，省略该字段，不可据此判断账号是否公开"

addedOutput schema / properties / items / items / properties / received_like_count / default
```
Added value: +null
```

changedOutput schema / properties / items / items / properties / received_like_count / description

Previous value: -"用户作品累计获赞数；当前不可用时为 null"New value: +"用户作品累计获赞数；未知时省略"

addedOutput schema / properties / items / items / properties / verified / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / items / items / properties / verified / default
```
Added value: +null
```

changedOutput schema / properties / items / items / properties / verified / description

Previous value: -"用户是否为认证账号"New value: +"用户是否为认证账号；未知时省略"

removedOutput schema / properties / items / items / properties / verified / type
```
Removed value: -"boolean"
```

changedOutput schema / properties / items / items / required

Previous value: -[
-  "user_id",
-  "tiktok_id",
-  "name",
-  "avatar_url",
-  "profile_url",
-  "bio",
-  "verified",
-  "private_account",
-  "follower_count",
-  "following_count",
-  "received_like_count",
-  "posted_content_count"
-]New value: +[
+  "user_id",
+  "tiktok_id",
+  "name",
+  "avatar_url",
+  "profile_url",
+  "bio"
+]

AddedOct 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond readOnlyHint/openWorldHint it discloses concrete behavior: which fields are omitted (private_account, following_count, posted_content_count), the pagination rule (continue only while next_page_token is non-empty), and downstream chaining (non-empty tiktok_id / profile_url can be fed to the profile and posts tools). These are non-obvious traits the annotations do not carry.

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 dense semicolon-separated clauses each carry information. There is mild redundancy in restating the two chaining identifiers (tiktok_id and profile_url) in near-identical clauses, which costs a little tightness.

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 an output schema present, return values need not be spelled out, yet the description still adds the field-omission caveat and the identifier-chaining guidance an agent needs to actually use the results. Nothing essential is missing for a read-only search 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 description coverage is 100%, so keyword and page_token are already documented (including the non-empty constraint and the opaque-token rule). The description reinforces the pagination semantics of page_token ('是否继续翻页仅以 next_page_token 是否为空为准') and adds flow meaning, going slightly beyond the baseline.

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 (按非空搜索词搜索 TikTok 用户) plus the discovery intent (按用户名、昵称或品牌名查找候选用户). It clearly distinguishes itself from sibling search_posts and the get_user_info_* / get_user_posts_* tools, so an agent can select it without opening any schema.

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?

Gives an explicit use case (finding candidate users) and an explicit exclusion: '已知准确用户标识且只需上述后续数据时，使用对应入口，无需先搜索' — i.e. skip this tool and go straight to the profile/posts entry points. This is a genuine when/when-not routing rule with the alternative named.

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

All SocialDataX TikTok MCP tools Inspect

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

Need Help?