Skip to main content
Glama

SocialDataX 抖音 Douyin MCP

by com.52choujiang
OverviewDiscussionsAdmin

douyin_get_user_series_by_profile_url

Read-only

根据抖音主页长链接、短链接或分享文案获取用户短剧列表，支持 page_token 翻页。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_tokenNopage_token 是不透明分页令牌。首次请求留空；继续翻页时必须将上一次返回的完整 next_page_token 原样传入，作为 page_token 使用；只能用于同一用户短剧列表分页链路的下一页，不能跨能力或用户复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。
profile_urlYes抖音用户主页链接、用户短链接或用户分享文案；不要传作品链接。已知 sec_user_id 时优先使用 ID 入口

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes当前页短剧列表
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
next_page_tokenYes下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回。next_page_token 只能用于同一能力和同一分页链路，不能跨能力、作品、用户、评论、关键词或筛选条件复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / items / items / properties / author / properties / follower_count / description
      Previous value: -"粉丝数；当前不可用时为 null"New value: +"平台展示的粉丝数；当前不可用时为 null"
  2. Changed1 schema field changed
    • changedOutput schema / properties / items / items / properties / author / properties / sec_user_id / description
      Previous value: -"用户 sec_user_id；用户主页和作品工具可直接复用"New value: +"用户 sec_user_id；当前不可用时为空字符串"
  3. 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: -[
-  "items",
-  "next_page_token"
-]New value: +[
+  "items",
+  "next_page_token",
+  "points"
+]
  4. Changed2 schema fields changed
    • changedInput schema / properties / page_token / description
      Previous value: -"分页令牌。首次请求留空；继续翻页时原样传入上一次返回的 next_page_token；只能用于同一用户短剧列表分页链路的下一页，不能跨能力或用户复用"New value: +"page_token 是不透明分页令牌。首次请求留空；继续翻页时必须将上一次返回的完整 next_page_token 原样传入，作为 page_token 使用；只能用于同一用户短剧列表分页链路的下一页，不能跨能力或用户复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。"
    • changedOutput schema / properties / next_page_token / description
      Previous value: -"下一页分页令牌；为空表示没有更多结果"New value: +"下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回。next_page_token 只能用于同一能力和同一分页链路，不能跨能力、作品、用户、评论、关键词或筛选条件复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。"
  5. Changed3 schema fields changed
    • changedInput schema / properties / page_token / description
      Previous value: -"分页令牌。首次请求留空；继续翻页时原样传入上一次返回的 next_page_token；只能用于同一用户短剧列表分页链路的下一页，不能跨工具或用户复用"New value: +"分页令牌。首次请求留空；继续翻页时原样传入上一次返回的 next_page_token；只能用于同一用户短剧列表分页链路的下一页，不能跨能力或用户复用"
    • removedOutput schema / properties / items / items / properties / status_label
      Removed value: -{
-  "description": "短剧更新状态文案；当前不可用时为空字符串",
-  "type": "string"
-}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
-  "series_id",
-  "title",
-  "description",
-  "cover_image_url",
-  "share_url",
-  "create_time",
-  "update_time",
-  "play_count",
-  "collect_count",
-  "total_episode_count",
-  "updated_episode_count",
-  "status_label",
-  "author"
-]New value: +[
+  "series_id",
+  "title",
+  "description",
+  "cover_image_url",
+  "share_url",
+  "create_time",
+  "update_time",
+  "play_count",
+  "collect_count",
+  "total_episode_count",
+  "updated_episode_count",
+  "author"
+]
  6. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already disclose readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds that page_token pagination is supported, a behavioral detail not in the annotations, giving agents useful context for iterating through results.

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 states the resource, input variants, and pagination capability with no redundancy. It is properly front-loaded and every clause 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?

The output schema exists and the input schema fully documents both parameters, so the description only needs to convey the tool's purpose and main behavior. It does so adequately; a minor gap is not mentioning the sec_user_id alternative explicitly in the description, though the schema instructions cover it.

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?

With 100% schema description coverage, the parameter meanings are already fully documented. The main description only reiterates the profile URL formats and pagination without adding new semantic detail, matching the baseline for high coverage.

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 clearly states the tool retrieves a user's short drama/series list (用户短剧列表) from a Douyin profile URL, specifying long link, short link, or share text as inputs. It does not explicitly contrast with the sec_user_id-based sibling tool, so differentiation is implicit through the input type.

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

Usage Guidelines2/5

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

The description provides no direct guidance on when to use this tool versus alternatives such as douyin_get_user_series_by_sec_user_id. It only lists accepted input types and pagination support, without any conditions, exclusions, or references to sibling tools.

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