Skip to main content
Glama

SocialDataX 抖音 Douyin MCP

douyin_get_user_info_by_douyin_id

Read-only

根据用户主页展示的抖音号 douyin_id 获取用户资料。

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": {
      "douyin_id": "<douyin_id>"
    },
    "name": "douyin_get_user_info_by_douyin_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
douyin_idYes用户主页展示的公开抖音号 douyin_id;不要传昵称、搜索关键词、sec_user_id、用户主页链接或作品链接

Output Schema

NameRequiredDescriptionDefault
bioYes用户简介;当前不可用时为空字符串
nameYes用户昵称
genderYes性别:male 表示男,female 表示女,unknown 表示未知
pointsYes本次成功调用的积分消耗与账户积分余额。
user_idYes用户 user_id;当前不可用时为空字符串
verifiedYes用户是否为认证账号
douyin_idYes用户主页展示的抖音号;当前不可用时为空字符串
live_infoYes用户直播状态摘要;用户当前未直播时为 null
avatar_urlYes用户头像链接;当前不可用时为 null
ip_locationYesIP 属地;当前不可用时为空字符串
profile_urlYes用户主页链接;当前不可用时为 null
sec_user_idYes用户 sec_user_id;当前不可用时为空字符串
follower_countYes平台展示的粉丝数;当前不可用时为 null
following_countYes关注数;当前不可用时为 null
verification_labelYes用户认证文案;当前不可用时为空字符串
received_like_countYes用户内容累计收到的点赞数;当前不可用时为 null
posted_content_countYes用户已发布作品数量,包含视频、图文等作品;当前不可用时为 null
douyin_follower_countNo抖音单端粉丝数;当前不可用时为 null
cross_platform_follower_countNo关联平台合计粉丝数;当前不可用时为 null

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / points / description
      Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额,可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时,回退到本次预扣后的余额快照。余额可为负数。"
  2. 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
  3. Changed19 schema fields changed
    • addedOutput schema / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / bio / title
      Added value: +"Bio"
    • addedOutput schema / properties / cross_platform_follower_count / title
      Added value: +"Cross Platform Follower Count"
    • addedOutput schema / properties / douyin_follower_count / title
      Added value: +"Douyin Follower Count"
    • addedOutput schema / properties / douyin_id / title
      Added value: +"Douyin Id"
    • addedOutput schema / properties / follower_count / title
      Added value: +"Follower Count"
    • addedOutput schema / properties / following_count / title
      Added value: +"Following Count"
    • addedOutput schema / properties / gender / title
      Added value: +"Gender"
    • addedOutput schema / properties / ip_location / title
      Added value: +"Ip Location"
    • changedOutput schema / properties / live_info / anyOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "is_live": {
      -        "description": "用户当前是否正在直播",
      -        "type": "boolean"
      -      },
      -      "live_url": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "description": "直播间页面链接;当前不可用时为 null"
      -      },
      -      "online_user_count": {
      -        "anyOf": [
      -          {
      -            "type": "integer"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "description": "请求时直播间在线人数快照;当前不可用时为 null"
      -      },
      -      "room_id": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "description": "直播间 ID;当前不可用时为 null"
      -      }
      -    },
      -    "required": [
      -      "is_live",
      -      "room_id",
      -      "live_url",
      -      "online_user_count"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "is_live": {
      +        "description": "用户当前是否正在直播",
      +        "title": "Is Live",
      +        "type": "boolean"
      +      },
      +      "live_url": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "直播间页面链接;当前不可用时为 null",
      +        "title": "Live Url"
      +      },
      +      "online_user_count": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "请求时直播间在线人数快照;当前不可用时为 null",
      +        "title": "Online User Count"
      +      },
      +      "room_id": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "直播间 ID;当前不可用时为 null",
      +        "title": "Room Id"
      +      }
      +    },
      +    "required": [
      +      "is_live",
      +      "room_id",
      +      "live_url",
      +      "online_user_count"
      +    ],
      +    "title": "DouyinUserLiveInfoData",
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / posted_content_count / title
      Added value: +"Posted Content Count"
    • addedOutput schema / properties / profile_url / title
      Added value: +"Profile Url"
    • addedOutput schema / properties / received_like_count / title
      Added value: +"Received Like Count"
    • addedOutput schema / properties / sec_user_id / title
      Added value: +"Sec User Id"
    • addedOutput schema / properties / user_id / title
      Added value: +"User Id"
    • addedOutput schema / properties / verification_label / title
      Added value: +"Verification Label"
    • addedOutput schema / properties / verified / title
      Added value: +"Verified"
    • addedOutput schema / title
      Added value: +"DouyinUserInfoData"
  4. Changed3 schema fields changed
    • addedOutput schema / properties / cross_platform_follower_count
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "关联平台合计粉丝数;当前不可用时为 null"
      +}
    • addedOutput schema / properties / douyin_follower_count
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "抖音单端粉丝数;当前不可用时为 null"
      +}
    • changedOutput schema / properties / follower_count / description
      Previous value: -"粉丝数;当前不可用时为 null"New value: +"平台展示的粉丝数;当前不可用时为 null"
  5. Changed1 schema field changed
    • changedOutput schema / properties / sec_user_id / description
      Previous value: -"用户 sec_user_id;用户主页和作品工具可直接复用"New value: +"用户 sec_user_id;当前不可用时为空字符串"
  6. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that the lookup keys off the publicly displayed ID — nothing about result contents, failure behavior for missing/private accounts, or rate limits. That is acceptable given the annotations and the presence of an output schema, but it is not rich.

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?

One short sentence, front-loaded with the verb and identifier source, with zero redundant or hedging wording. Nothing could be removed without losing meaning.

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

Completeness3/5

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

For a single-parameter read tool with annotations and an output schema, the minimum is met, but the crowded sibling set of get_user_info_by_* variants makes the absence of routing guidance a real gap. An agent still has to infer the choice from the tool name alone.

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% and the single parameter is fully documented in the schema, including the negatives (do not pass nickname, keywords, sec_user_id, or links). The description's phrase 用户主页展示的 repeats that same meaning rather than adding new semantics, so the baseline 3 applies.

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

Purpose4/5

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

The description uses the concrete verb-and-resource pattern 获取+用户资料 and identifies the exact key (douyin_id displayed on the user's homepage). It is clear what the tool returns, but it never names the sibling variants douyin_get_user_info_by_profile_url / by_sec_user_id, so the differentiation is left to the tool name rather than the description.

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

Usage Guidelines3/5

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

Usage is only implied: the description ties the tool to the homepage-visible douyin_id, which hints at when it applies, but it gives no explicit when-to-use/when-not guidance and does not point to the URL or sec_user_id alternatives. The exclusion of nicknames, sec_user_id, and links appears only in the schema's parameter description, not in the tool description.

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