SocialDataX 微博 Weibo MCP

weibo_get_user_posts_by_user_id

Read-only

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

Input Schema

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

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.

Changed1 schema field changedOct 19, 2026

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

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

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.5/5.0

Behavior3/5

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

With readOnlyHint=true and openWorldHint=true already covering the safety profile, the description minimally adds that pagination is supported. It does not mention rate limits, result ordering, or how many posts are returned per page, so it adds only modest context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the operation and its pagination capability are stated immediately. It is appropriately sized for a tool whose parameters are fully documented elsewhere.

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?

An output schema exists, so return values need not be re-described, and annotations carry the read-only/open-world profile. For a two-parameter lookup tool, the description supplies what an agent needs to call it correctly, with only sibling differentiation left implicit.

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 the schema already fully documents both user_id and the opaque page_token handling. The description only echoes "支持 page_token 翻页" without adding any semantics beyond the schema, which is the expected 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?

The description gives a specific verb+resource ("获取微博用户帖子列表") scoped by user_id, which is enough to separate it from siblings like weibo_get_user_posts_by_profile_url and weibo_get_post_comments_by_post_id. However it never explicitly names the profile_url alternative, so the differentiation relies on the tool name and params rather than the prose.

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?

Usage is only implied: you call this when you have a user_id. There is no statement of when to prefer it over weibo_get_user_posts_by_profile_url, nor any exclusions relative to weibo_search_posts. The page_token continuation hint lives mostly in the schema, not the description.

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?