SocialDataX 抖音 Douyin MCP

douyin_get_user_info_by_sec_user_id

Read-only

根据抖音用户 sec_user_id 获取用户资料；已知 sec_user_id 时优先使用此入口。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sec_user_id`	Yes	抖音用户 sec_user_id，不透明标识；请传实际字段值，可从结果中的 sec_user_id 或 author.sec_user_id 复用；不要传公开抖音号 douyin_id、字段名或占位文本；只有主页链接时使用 profile_url 入口

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"

Changed2 schema fields changedSep 3, 2026

changedInput schema / properties / sec_user_id / description

Previous value: -"抖音用户 sec_user_id；可从 author.sec_user_id 或用户资料结果中的 sec_user_id 继续复用"New value: +"抖音用户 sec_user_id，不透明标识；请传实际字段值，可从结果中的 sec_user_id 或 author.sec_user_id 复用；不要传公开抖音号 douyin_id、字段名或占位文本；只有主页链接时使用 profile_url 入口"

changedOutput schema / properties / sec_user_id / description

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

Changed2 schema fields changedAug 17, 2026

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: -[
-  "user_id",
-  "sec_user_id",
-  "name",
-  "avatar_url",
-  "profile_url",
-  "bio",
-  "verification_label",
-  "verified",
-  "follower_count",
-  "following_count",
-  "received_like_count",
-  "douyin_id",
-  "ip_location",
-  "gender",
-  "posted_content_count",
-  "live_info"
-]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",
+  "ip_location",
+  "gender",
+  "posted_content_count",
+  "live_info",
+  "points"
+]

Changed2 schema fields changedJun 29, 2026

addedOutput schema / properties / live_info

Added value: +{
+  "anyOf": [
+    {
+      "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"
+    }
+  ],
+  "description": "用户直播状态摘要；用户当前未直播时为 null"
+}

changedOutput schema / 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",
-  "ip_location",
-  "gender",
-  "posted_content_count"
-]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",
+  "ip_location",
+  "gender",
+  "posted_content_count",
+  "live_info"
+]

First observedMay 18, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read operation. The description adds the behavioral note that sec_user_id is an opaque identifier and that the actual field value should be reused from results, which is useful. However, it doesn't describe output shape or any rate-limit/error behavior, but with annotations covering safety, a 3 is appropriate.

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 a single sentence that front-loads the core purpose and then adds the key usage preference. The parameter description is also concise and dense with actionable guidance. No wasted words.

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 single-parameter read tool with a rich schema description and output schema present, the description is nearly complete. It covers what the tool does, when to use it, and how to supply the parameter correctly. The only minor gap is not explicitly naming sibling alternatives, but the guidance is sufficient for an agent to select correctly.

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 the schema already documents the parameter. The description adds meaningful semantics beyond the schema: it clarifies that sec_user_id is opaque, instructs to pass the actual field value from results, and explicitly warns against passing douyin_id, field names, or placeholder text. This goes beyond the schema's basic description.

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 states a specific verb and resource: '根据抖音用户 sec_user_id 获取用户资料' (get user profile by sec_user_id). It also adds a usage preference ('已知 sec_user_id 时优先使用此入口'), which helps distinguish it from sibling tools like douyin_get_user_info_by_douyin_id and douyin_get_user_info_by_profile_url. However, it doesn't explicitly name those alternatives, so it's clear but not fully differentiated.

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

Usage Guidelines4/5

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

The description gives clear context: use this entry when sec_user_id is already known. The parameter description adds an explicit exclusion: don't pass douyin_id, field names, or placeholder text, and use profile_url entry when only a profile link is available. This is strong guidance, though it doesn't explicitly name the sibling tools for those alternatives.

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?