Skip to main content
Glama

SocialDataX 抖音 Douyin MCP

by com.52choujiang
OverviewDiscussionsAdmin

douyin_get_user_info_by_profile_url

Read-only

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_urlYes抖音用户主页链接、用户短链接或用户分享文案；不要传作品链接。已知 sec_user_id 时优先使用 ID 入口

Output Schema

TableJSON 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / sec_user_id / description
      Previous value: -"用户 sec_user_id；用户主页和作品工具可直接复用"New value: +"用户 sec_user_id；当前不可用时为空字符串"
  2. Changed2 schema fields changed
    • 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"
+]
  3. Changed2 schema fields changed
    • 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"
+]
  4. First observed

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the read-only and externally-changing data aspects are covered. The description adds input-format context but does not disclose further behavior such as error handling, rate limits, or result volatility; 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?

The main description is one short, front-loaded sentence that names the action and accepted input forms with no filler or repetition. Every part contributes directly to understanding what the tool does.

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

Completeness5/5

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

The tool is simple with one required parameter, has a full output schema, and the parameter description covers the important exclusions and routing guidance. Combined with the read-only and open-world annotations, nothing essential is missing for an agent to select and invoke the tool correctly.

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 profile_url parameter description already fully documents allowed input types, the prohibition on video links, and the preference for ID-based entry. The main description repeats essentially the same input information without adding meaning beyond what the schema provides.

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 uses a specific verb ('获取') and resource ('用户资料'), and precisely scopes the input to '主页长链接、短链接或分享文案'. This distinguishes it from the ID-based sibling tools and the video/series tools because it is clearly about fetching profile data from URL or share-text forms.

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

Usage Guidelines5/5

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

The parameter description explicitly states when not to use this tool ('不要传作品链接') and gives a routing preference ('已知 sec_user_id 时优先使用 ID 入口'), which tells the agent to prefer the sec_user_id-based sibling when appropriate. The main description also makes clear that this tool is for profile URLs or share text, so the when-to-use condition is explicit.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources