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. Changed1 schema field changed
    • changedOutput schema / properties / items / items / properties / author / properties / follower_count / description
      Previous value: -"粉丝数；当前不可用时为 null"New value: +"平台展示的粉丝数；当前不可用时为 null"
  2. 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；当前不可用时为空字符串"
  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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only nature is covered. The description adds the specific behavioral detail that pagination is supported via page_token, which is not in the annotations. It does not contradict the annotations and provides useful operational context for the agent.

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 front-loads the resource and input, and includes the pagination key point. There is zero filler or repetition, making it efficient and easy to parse.

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 high schema coverage, an output schema, and read-only annotations, the description is largely sufficient for an agent to invoke the tool correctly. It does not explain the distinction from the profile_url sibling, but that is not necessary for calling this tool correctly. The missing guidance on when to choose sec_user_id vs profile_url is a minor gap but not a blocker.

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%, with both sec_user_id and page_token having detailed descriptions in the schema. The tool description simply restates the main input and pagination support without adding any new meaning beyond what the schema already provides. Thus 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 verb '获取' (get) and the specific resource '该用户短剧列表' (the user's short drama series list), with the input being sec_user_id. It distinguishes from sibling tools like douyin_get_user_posted_videos_by_sec_user_id and douyin_get_user_info_by_sec_user_id by naming the series list explicitly, and the name already disambiguates from the profile_url variant.

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 does not explicitly state when to use this tool versus alternatives. It implies usage via the sec_user_id input, but there is no mention of the sibling tool douyin_get_user_series_by_profile_url or guidance on when to prefer one entry point over the other. The pagination note is helpful but does not address selection criteria.

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