SocialDataX 抖音 Douyin MCP

douyin_get_user_series_by_sec_user_id

Read-only

根据抖音用户 sec_user_id 获取该用户短剧列表，支持 page_token 翻页。

Input Schema

Name	Required	Description	Default
`page_token`	No	page_token 是不透明分页令牌。首次请求留空；继续翻页时必须将上一次返回的完整 next_page_token 原样传入，作为 page_token 使用；只能用于同一用户短剧列表分页链路的下一页，不能跨能力或用户复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。
`sec_user_id`	Yes	抖音用户 sec_user_id，不透明标识；请传实际字段值，可从结果中的 sec_user_id 或 author.sec_user_id 复用；不要传公开抖音号 douyin_id、字段名或占位文本；只有主页链接时使用 profile_url 入口

Output Schema

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

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
```
Changed28 schema fields changedNov 3, 2026
- addedOutput schema / properties / items / items / properties / author / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / items / items / properties / author / properties / bio / title
```
Added value: +"Bio"
```
- addedOutput schema / properties / items / items / properties / author / properties / douyin_id / title
```
Added value: +"Douyin Id"
```
- addedOutput schema / properties / items / items / properties / author / properties / follower_count / title
```
Added value: +"Follower Count"
```
- addedOutput schema / properties / items / items / properties / author / properties / following_count / title
```
Added value: +"Following Count"
```
- addedOutput schema / properties / items / items / properties / author / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / items / items / properties / author / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / items / items / properties / author / properties / received_like_count / title
```
Added value: +"Received Like Count"
```
- addedOutput schema / properties / items / items / properties / author / properties / sec_user_id / title
```
Added value: +"Sec User Id"
```
- addedOutput schema / properties / items / items / properties / author / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / items / items / properties / author / properties / verification_label / title
```
Added value: +"Verification Label"
```
- addedOutput schema / properties / items / items / properties / author / properties / verified / title
```
Added value: +"Verified"
```
- addedOutput schema / properties / items / items / properties / author / title
```
Added value: +"DouyinAuthorData"
```
- addedOutput schema / properties / items / items / properties / collect_count / title
```
Added value: +"Collect Count"
```
- addedOutput schema / properties / items / items / properties / cover_image_url / title
```
Added value: +"Cover Image Url"
```
- addedOutput schema / properties / items / items / properties / create_time / title
```
Added value: +"Create Time"
```
- addedOutput schema / properties / items / items / properties / description / title
```
Added value: +"Description"
```
- addedOutput schema / properties / items / items / properties / play_count / title
```
Added value: +"Play Count"
```
- addedOutput schema / properties / items / items / properties / series_id / title
```
Added value: +"Series Id"
```
- addedOutput schema / properties / items / items / properties / share_url / title
```
Added value: +"Share Url"
```
- addedOutput schema / properties / items / items / properties / title / title
```
Added value: +"Title"
```
- addedOutput schema / properties / items / items / properties / total_episode_count / title
```
Added value: +"Total Episode Count"
```
- addedOutput schema / properties / items / items / properties / update_time / title
```
Added value: +"Update Time"
```
- addedOutput schema / properties / items / items / properties / updated_episode_count / title
```
Added value: +"Updated Episode Count"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"DouyinSeriesItemData"
```
- addedOutput schema / properties / items / title
```
Added value: +"Items"
```
- addedOutput schema / properties / next_page_token / title
```
Added value: +"Next Page Token"
```
- addedOutput schema / title
```
Added value: +"DouyinUserSeriesResult"
```
Changed1 schema field changedSep 15, 2026
- changedOutput schema / properties / items / items / properties / author / 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 / items / items / properties / author / 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: -[
-  "items",
-  "next_page_token"
-]New value: +[
+  "items",
+  "next_page_token",
+  "points"
+]

Changed2 schema fields changedJun 4, 2026

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 只能用于同一能力和同一分页链路，不能跨能力、作品、用户、评论、关键词或筛选条件复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。"

Changed3 schema fields changedMay 20, 2026

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"
+]

AddedMay 19, 2026

TDQS

A3.6/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 safety profile is covered. The description adds only the pagination capability, while the detailed page_token chaining rules live in the schema rather than the description.

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?

A single front-loaded sentence identifies the resource, the required identifier, and pagination with zero filler. Nothing is repeated or wasted.

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 read-only, two-parameter list tool with a full schema and an output schema, the definition covers the essential scope and pagination behavior. The only meaningful omission is explicit routing to the profile_url sibling, which is a usage gap rather than a missing return-value explanation.

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%, so both parameters are already fully documented in the schema, including the strict page_token reuse rules. The description merely names sec_user_id and page_token and adds no meaning beyond that baseline.

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?

Names a specific verb (get/list), resource (the user's short-drama series list), and the key identifier (sec_user_id). It implicitly distinguishes itself from douyin_get_user_series_by_profile_url through the sec_user_id entry point, but it never names that sibling or states the routing rule explicitly.

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 implies when to use it (when you have a sec_user_id) and mentions page_token pagination, but gives no explicit when-not guidance and does not point agents to the profile_url variant when only a profile link is available.

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?