Skip to main content
Glama

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 可直接传给用户资料和用户作品工具;仅使用非空标识调用对应入口。已知准确用户标识且只需上述后续数据时,使用对应入口,无需先搜索。

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": "tiktok_search_users"
  }
}

Input Schema

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

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / keyword / description
      Previous value: -"keyword 为非空搜索词,可传用户名、账号名、昵称、品牌名或机构名,例如 teamtrump、campinglife;不要传用户主页链接、作品链接、用户数字 ID、post_id 或分页令牌 page_token。"New value: +"keyword 为非空搜索词,可传用户名、账号名、昵称、品牌名或机构名,例如 campinglife、outdoor;不要传用户主页链接、作品链接、用户数字 ID、post_id 或分页令牌 page_token。"
  2. Changed2 schema fields changed
    • changedOutput schema / properties / points / description
      Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额,可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时,回退到本次预扣后的余额快照。余额可为负数。"
  3. Changed2 schema fields changed
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额,可为负数。"
    • removedOutput schema / properties / points / properties / balance / minimum
      Removed value: -0
  4. Changed16 schema fields changed
    • addedOutput schema / properties / items / items / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / items / items / properties / bio / title
      Added value: +"Bio"
    • addedOutput schema / properties / items / items / properties / follower_count / title
      Added value: +"Follower Count"
    • addedOutput schema / properties / items / items / properties / following_count / title
      Added value: +"Following Count"
    • addedOutput schema / properties / items / items / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / items / items / properties / posted_content_count / title
      Added value: +"Posted Content Count"
    • addedOutput schema / properties / items / items / properties / private_account / title
      Added value: +"Private Account"
    • addedOutput schema / properties / items / items / properties / profile_url / title
      Added value: +"Profile Url"
    • addedOutput schema / properties / items / items / properties / received_like_count / title
      Added value: +"Received Like Count"
    • addedOutput schema / properties / items / items / properties / tiktok_id / title
      Added value: +"Tiktok Id"
    • addedOutput schema / properties / items / items / properties / user_id / title
      Added value: +"User Id"
    • addedOutput schema / properties / items / items / properties / verified / title
      Added value: +"Verified"
    • addedOutput schema / properties / items / items / title
      Added value: +"TikTokPublicUserSearchItem"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / properties / next_page_token / title
      Added value: +"Next Page Token"
    • addedOutput schema / title
      Added value: +"TikTokPublicUserSearchResult"
  5. Changed15 schema fields changed
    • 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"
      +]
  6. Added

TDQS

A4.5/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, it discloses that results omit private_account, following_count and posted_content_count, and that paging termination is determined solely by an empty next_page_token — real behavioral context an agent can't get from annotations. It stops short of describing result ordering, limits, or rate behavior.

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 and the alternative path are front-loaded, and every clause carries operational value (omitted fields, paging rule, identifier hand-off). It is dense with semicolons and slightly overloaded for a search tool, but no sentence is filler.

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

Completeness4/5

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

Given an output schema exists, return fields need not be re-explained, and the description still covers pagination semantics and how to chain results into profile/post tools. Only minor gaps remain around ranking or result volume expectations.

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% and already documents both parameters, but the description still adds cross-cutting constraints: what must not be passed as keyword (profile/post URLs, numeric user ID, post_id, page_token) and that page_token must be echoed unmodified and never reused across keywords or request chains. That reinforces semantics the schema states separately.

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 resource ('按非空搜索词搜索 TikTok 用户') plus the matching modes (username, nickname, brand name) and the return shape (public user profiles with page_token paging). This is clearly distinguishable from the search_posts / search_suggestions / get_user_info siblings.

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 explicit routing: search first when the identifier is unknown, but if an exact user identifier is already known and only profile/posts data is needed, call the corresponding sibling entry directly without searching. It also names the downstream tools the returned tiktok_id/profile_url can feed, and warns to use only non-empty identifiers.

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