Skip to main content
Glama

SocialDataX 抖音 Douyin MCP

by com.52choujiang
OverviewDiscussionsAdmin

douyin_get_user_series_by_sec_user_id

Read-only

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

Input Schema

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

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. Changed2 schema fields changed
    • 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；当前不可用时为空字符串"
  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: -[
-  "items",
-  "next_page_token"
-]New value: +[
+  "items",
+  "next_page_token",
+  "points"
+]
  3. 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 只能用于同一能力和同一分页链路，不能跨能力、作品、用户、评论、关键词或筛选条件复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。"
  4. 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"
+]
  5. Added

TDQS

A4/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint annotations already establish the safety and open-world profile, so the description only needs to add behavior beyond that. It adds that pagination via page_token is supported, which is useful, but it does not disclose rate limits, potential empty results, or other behavioral details. This is acceptable but not rich.

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, focused sentence that front-loads the primary purpose and then states pagination support. There is no filler, no repetition of the tool name, 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?

For a read-only paginated list tool, the combination of description, detailed parameter schema, and annotations is largely sufficient. The output schema covers return values, and readOnlyHint covers safety. The only minor gap is that the main description does not explicitly route users to the profile_url sibling, though the parameter description partially compensates.

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 input schema has 100% parameter description coverage and already explains both sec_user_id and page_token in detail, including opaque-token reuse rules and what not to pass. The description itself only repeats the pagination concept and adds no extra parameter-level meaning, so the baseline of 3 applies.

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 a specific resource ('该用户短剧列表' / user's short-drama series list), and clearly identifies the required input (sec_user_id). It also distinguishes itself from sibling tools like douyin_get_user_info_by_sec_user_id and douyin_get_user_posted_videos_by_sec_user_id by naming the series/short-drama list resource.

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

Usage Guidelines4/5

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

The description gives clear context for when to use the tool: when you have a Douyin sec_user_id and need that user's series list. It does not explicitly name the profile_url sibling in the main description, but the sec_user_id parameter description provides the key exclusion: if only a profile URL is available, use the profile_url entry.

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