SocialDataX 微博 Weibo MCP

weibo_get_user_posts_by_user_id

Read-only

根据 user_id 获取微博用户帖子列表，支持 page_token 翻页。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user_id`	Yes	微博用户 user_id；可从作者信息或用户资料结果中的非空 user_id 复用。
`page_token`	No	微博用户帖子列表分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一用户帖子列表分页链路，不能跨用户复用。

Output Schema

TableJSON 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 changedAug 26, 2026

addedOutput schema / properties / items / items / properties / images

Added value: +{
+  "description": "图片列表，包含链接及宽高；无图时为空数组。",
+  "items": {
+    "properties": {
+      "height": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "图片高度，像素；不可用时为 null。"
+      },
+      "url": {
+        "description": "图片链接。",
+        "type": "string"
+      },
+      "width": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "图片宽度，像素；不可用时为 null。"
+      }
+    },
+    "required": [
+      "url",
+      "width",
+      "height"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "post_id",
-  "content",
-  "publish_time",
-  "post_url",
-  "like_count",
-  "comment_count",
-  "repost_count",
-  "play_count",
-  "image_urls",
-  "topic_tags",
-  "author"
-]New value: +[
+  "post_id",
+  "content",
+  "publish_time",
+  "post_url",
+  "like_count",
+  "comment_count",
+  "repost_count",
+  "play_count",
+  "image_urls",
+  "images",
+  "topic_tags",
+  "author"
+]

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 changedJul 2, 2026

addedOutput schema / properties / items / items / properties / topic_tags

Added value: +{
+  "description": "微博帖子话题标签列表；无标签时为空数组。",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "description": "话题标签名称。",
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "post_id",
-  "content",
-  "publish_time",
-  "post_url",
-  "like_count",
-  "comment_count",
-  "repost_count",
-  "play_count",
-  "image_urls",
-  "author"
-]New value: +[
+  "post_id",
+  "content",
+  "publish_time",
+  "post_url",
+  "like_count",
+  "comment_count",
+  "repost_count",
+  "play_count",
+  "image_urls",
+  "topic_tags",
+  "author"
+]

Changed1 schema field changedJun 24, 2026

changedOutput schema / properties / items / items / properties / play_count / description

Previous value: -"播放数；不可用时为 null。"New value: +"帖子内视频播放数；没有视频或上游未返回时为 null，不是帖子浏览数。"

Changed2 schema fields changedJun 24, 2026

addedOutput schema / properties / items / items / properties / play_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "播放数；不可用时为 null。"
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "post_id",
-  "content",
-  "publish_time",
-  "post_url",
-  "like_count",
-  "comment_count",
-  "repost_count",
-  "image_urls",
-  "author"
-]New value: +[
+  "post_id",
+  "content",
+  "publish_time",
+  "post_url",
+  "like_count",
+  "comment_count",
+  "repost_count",
+  "play_count",
+  "image_urls",
+  "author"
+]

First observedJun 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, covering the safe-read nature. The description adds that pagination uses page_token, but detailed token behavior lives in the schema rather than the description, and no other runtime traits like ordering or first-page behavior are disclosed.

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 with no filler. It states the resource, the key parameter, and pagination support efficiently.

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 low-complexity, read-only list tool with an output schema and fully documented parameters, the description is nearly sufficient. It lacks an explicit pointer to the profile_url sibling, but the user_id-based naming and description make correct invocation clear.

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%, including a detailed contract for page_token as an opaque token. The description adds no meaning beyond the schema: it simply says the tool uses user_id and supports page_token pagination.

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 specifies a clear verb and resource: getting a Weibo user's post list by user_id. It also mentions page_token pagination, and the 'by_user_id' naming distinguishes it from the sibling 'by_profile_url' tool.

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 use when a user_id is available, but it does not explicitly contrast this tool with weibo_get_user_posts_by_profile_url or state when not to use it. The selection criterion is clear but largely left to inference from the tool name.

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

All SocialDataX 微博 Weibo 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?