SocialDataX 抖音 Douyin MCP

douyin_get_user_info_by_profile_url

Read-only

根据抖音主页长链接、短链接或分享文案获取用户资料。

Input Schema

Name	Required	Description	Default
`profile_url`	Yes	抖音用户主页链接、用户短链接或用户分享文案；不要传作品链接。已知 sec_user_id 时优先使用 ID 入口

Output 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.

Changed2 schema fields changedNov 4, 2026

changedOutput schema / properties / points / description

Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"

changedOutput schema / properties / points / properties / balance / description

Previous value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"

Changed2 schema fields changedNov 4, 2026
- changedOutput schema / properties / points / properties / balance / description
```
Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"
```
- removedOutput schema / properties / points / properties / balance / minimum
```
Removed value: -0
```

Changed19 schema fields changedNov 3, 2026

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"
```

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；当前不可用时为空字符串"

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

B3.4/5.0

Behavior2/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. Beyond that, the description discloses no behavior at all: nothing about authentication, rate limits, failure modes for invalid or private profiles, or what '用户资料' contains. It restates the input forms, which the schema also carries.

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, front-loaded sentence with no filler. The accepted input forms come immediately after the verb and resource, so nothing needs re-reading.

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?

An output schema exists, so return values need not be explained, and annotations cover the read-only, open-world profile. For a single fully documented parameter, the description covers purpose and accepted inputs adequately; only the routing to the sec_user_id and douyin_id siblings is missing.

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 already documents accepted link types plus the exclusion of 作品链接, so the schema does the heavy lifting. The description echoes the same input forms without adding syntax, format, or fallback detail beyond what is already structured.

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 (获取用户资料) and enumerates the accepted input forms: long homepage link, short link, and share text. Combined with the tool name, this makes it distinguishable from douyin_get_user_info_by_sec_user_id and douyin_get_user_info_by_douyin_id, though the description itself never names those siblings as alternatives.

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 usage context is only implied: the reader infers this is the URL-based entry point when no ID is available. The explicit routing rule ('已知 sec_user_id 时优先使用 ID 入口' and '不要传作品链接') lives in the parameter schema, not the description, so the description itself gives no when-not 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?