SocialDataX 抖音 Douyin MCP

douyin_get_user_info_by_profile_url

Read-only

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`profile_url`	Yes	抖音用户主页链接、用户短链接或用户分享文案；不要传作品链接。已知 sec_user_id 时优先使用 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；当前不可用时为空字符串"

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.8/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, which already communicate that this is a safe, read-only operation. The description adds no additional behavioral context beyond stating it retrieves user info, so it does not exceed what annotations provide but also does not contradict them.

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, concise sentence that states the action and input types without any unnecessary words. It is front-loaded and efficiently conveys the core purpose.

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 the tool's simplicity (one parameter), the presence of an output schema, and annotations covering read-only behavior, the description is adequate. It does not explain return format or error conditions, but these are covered by the output schema and the tool's low complexity.

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 single parameter 'profile_url' has 100% schema description coverage, including details on accepted formats, exclusions, and a recommendation to prefer the ID entry. The description itself adds nothing beyond the schema, so the baseline of 3 is appropriate.

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?

The description clearly states the tool's purpose: to retrieve user profile data based on a Douyin profile URL, specifying accepted formats (long link, short link, share text). It distinguishes itself from sibling ID-based tools by focusing on URL input, making its function unambiguous.

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 itself provides no explicit guidance on when to use this tool versus alternatives. However, the schema parameter description includes clear instructions: do not pass video links and prefer the ID entry when sec_user_id is known. This guidance is present in the schema but not in the description, so the description alone is lacking.

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?