SocialDataX 抖音 Douyin MCP

douyin_get_user_info_by_douyin_id

Read-only

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`douyin_id`	Yes	用户主页展示的公开抖音号 douyin_id；不要传昵称、搜索关键词、sec_user_id、用户主页链接或作品链接

Output Schema

TableJSON Schema

Name	Required	Description
`bio`	Yes	用户简介；当前不可用时为空字符串
`name`	Yes	用户昵称
`gender`	Yes	性别：male 表示男，female 表示女，unknown 表示未知
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`user_id`	Yes	用户 user_id；当前不可用时为空字符串
`verified`	Yes	用户是否为认证账号
`douyin_id`	Yes	用户主页展示的抖音号；当前不可用时为空字符串
`live_info`	Yes	用户直播状态摘要；用户当前未直播时为 null
`avatar_url`	Yes	用户头像链接；当前不可用时为 null
`ip_location`	Yes	IP 属地；当前不可用时为空字符串
`profile_url`	Yes	用户主页链接；当前不可用时为 null
`sec_user_id`	Yes	用户 sec_user_id；当前不可用时为空字符串
`follower_count`	Yes	平台展示的粉丝数；当前不可用时为 null
`following_count`	Yes	关注数；当前不可用时为 null
`verification_label`	Yes	用户认证文案；当前不可用时为空字符串
`received_like_count`	Yes	用户内容累计收到的点赞数；当前不可用时为 null
`posted_content_count`	Yes	用户已发布作品数量，包含视频、图文等作品；当前不可用时为 null
`douyin_follower_count`	No	抖音单端粉丝数；当前不可用时为 null
`cross_platform_follower_count`	No	关联平台合计粉丝数；当前不可用时为 null

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 15, 2026

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"

Changed1 schema field changedSep 3, 2026

changedOutput schema / properties / sec_user_id / description

Previous value: -"用户 sec_user_id；用户主页和作品工具可直接复用"New value: +"用户 sec_user_id；当前不可用时为空字符串"

AddedAug 17, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds no additional behavioral detail such as data freshness, rate limits, or failure behavior, but it does not contradict the annotations.

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 with no filler; the essential identifier constraint is front-loaded and the schema adds the negative examples. Every word earns its place.

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?

For a one-parameter read-only lookup with an output schema and safety annotations, the description is nearly complete. It misses only an explicit pointer to the alternate-identifier sibling tools, but that is not essential for making a correct call.

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?

The schema already covers 100% of the single parameter, including its format and exclusions, so the description adds no new parameter semantics. 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?

States a specific action ('获取用户资料' – get user profile) and a precise resource keyed by the homepage-displayed douyin_id. This distinguishes it from sibling tools that use profile_url or sec_user_id.

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?

The description implies when to use the tool – when you have the douyin_id shown on the user's homepage – but it never names alternatives such as douyin_get_user_info_by_sec_user_id or douyin_get_user_info_by_profile_url. The schema's 'do not pass' list helps, but the description itself provides no explicit when-not-to-use guidance.

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 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?