SocialDataX 今日头条 MCP

toutiao_get_user_posts_by_user_id

Read-only

读取头条用户发布的作品；已有数字用户 ID 时使用本工具，有主页链接时使用按主页链接查询的工具。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_id": "<user_id>"
    },
    "name": "toutiao_get_user_posts_by_user_id"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	Yes	头条数字用户 ID，可取用户信息或内容作者的 author.user_id；有主页链接时使用 toutiao_get_user_posts_by_profile_url。
`page_token`	No	上一页返回的分页令牌；首次留空，不能跨用户或作品类型复用。
`content_type`	No	作品筛选：all、article、video、micro_post。	all

Output Schema

Name	Required	Description
`items`	Yes	用户发布的作品列表。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`next_page_token`	Yes	下一页分页令牌；为空表示结束。

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

Changed26 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 / 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 / user_id / title
```
Added value: +"User Id"
```
addedOutput schema / properties / items / items / properties / author / title
```
Added value: +"ToutiaoUserPostAuthor"
```
addedOutput schema / properties / items / items / properties / comment_count / title
```
Added value: +"Comment Count"
```
addedOutput schema / properties / items / items / properties / content / title
```
Added value: +"Content"
```
addedOutput schema / properties / items / items / properties / content_type / title
```
Added value: +"Content Type"
```
addedOutput schema / properties / items / items / properties / cover_image_url / title
```
Added value: +"Cover Image Url"
```
addedOutput schema / properties / items / items / properties / images / items / properties / height / title
```
Added value: +"Height"
```
addedOutput schema / properties / items / items / properties / images / items / properties / url / title
```
Added value: +"Url"
```
addedOutput schema / properties / items / items / properties / images / items / properties / width / title
```
Added value: +"Width"
```
addedOutput schema / properties / items / items / properties / images / items / title
```
Added value: +"ToutiaoImageData"
```
addedOutput schema / properties / items / items / properties / images / title
```
Added value: +"Images"
```
addedOutput schema / properties / items / items / properties / is_pinned / title
```
Added value: +"Is Pinned"
```
addedOutput schema / properties / items / items / properties / like_count / title
```
Added value: +"Like Count"
```
addedOutput schema / properties / items / items / properties / post_id / title
```
Added value: +"Post Id"
```
addedOutput schema / properties / items / items / properties / post_url / title
```
Added value: +"Post Url"
```
addedOutput schema / properties / items / items / properties / publish_time / title
```
Added value: +"Publish Time"
```
addedOutput schema / properties / items / items / properties / read_count / title
```
Added value: +"Read Count"
```
addedOutput schema / properties / items / items / properties / title / title
```
Added value: +"Title"
```

changedOutput schema / properties / items / items / properties / video / anyOf

Previous value: -[
-  {
-    "properties": {
-      "duration_ms": {
-        "description": "视频时长，单位毫秒。",
-        "type": "integer"
-      },
-      "height": {
-        "description": "视频高度，像素。",
-        "type": "integer"
-      },
-      "video_url": {
-        "description": "视频播放链接，有效期有限，建议获取后及时使用。",
-        "type": "string"
-      },
-      "width": {
-        "description": "视频宽度，像素。",
-        "type": "integer"
-      }
-    },
-    "required": [
-      "video_url",
-      "duration_ms",
-      "width",
-      "height"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "duration_ms": {
+        "description": "视频时长，单位毫秒。",
+        "title": "Duration Ms",
+        "type": "integer"
+      },
+      "height": {
+        "description": "视频高度，像素。",
+        "title": "Height",
+        "type": "integer"
+      },
+      "video_url": {
+        "description": "视频播放链接，有效期有限，建议获取后及时使用。",
+        "title": "Video Url",
+        "type": "string"
+      },
+      "width": {
+        "description": "视频宽度，像素。",
+        "title": "Width",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "video_url",
+      "duration_ms",
+      "width",
+      "height"
+    ],
+    "title": "ToutiaoVideoData",
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / items / items / title
```
Added value: +"ToutiaoUserPostItem"
```
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: +"ToutiaoUserPostsResult"
```

Changed1 schema field changedOct 19, 2026

addedOutput schema / properties / items / items / properties / is_pinned

Added value: +{
+  "default": false,
+  "description": "是否在用户主页置顶。",
+  "type": "boolean"
+}

First observedOct 16, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and openness profile is covered. The description adds the ID-versus-URL routing constraint but says nothing about pagination limits, ordering, or result scope beyond what the schema already documents. With annotations carrying the main behavioral burden, a 3 is appropriate.

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 compact sentence with the resource stated first and the routing condition immediately after. Every clause earns its place, and there is no redundant restatement of the tool name.

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 tool has three fully documented parameters, an output schema, and annotations covering read-only and open-world behavior. The description supplies the key selection rule relative to its sibling; only minor operational details such as pagination behavior are left implicit, which is acceptable given the output schema and complete parameter documentation.

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 schema itself explains user_id, page_token, and the content_type enum. The description reinforces the user_id routing rule but adds no syntax, format, or filtering semantics beyond what the structured fields already provide. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource in Chinese: reading works published by a Toutiao user, identified by numeric user ID. It explicitly distinguishes this tool from the sibling that queries by profile URL, so an agent can select between them without opening either schema.

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?

It gives an explicit routing rule: use this tool when a numeric user ID is available, and use the profile-URL-based tool when a homepage link is available. The alternative is named directly, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SocialDataX 今日头条 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?