SocialDataX 微博 Weibo MCP

weibo_search_posts

Read-only

按搜索词搜索微博帖子；当用户要按关键词或短语查找帖子时使用。已有帖子链接或 post_id 时使用对应帖子工具；已有用户主页链接或 user_id 时使用对应用户工具。支持 page_token 翻页。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`keyword`	Yes	微博帖子搜索词，可传关键词或短语；不要传帖子链接、用户主页链接、post_id、user_id 或 page_token。
`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"
+]

Changed1 schema field changedAug 19, 2026

changedInput schema / properties / keyword / description

Previous value: -"微博帖子搜索关键词；自然语言关键词可传品牌名、话题、人物名、内容需求或研究主题；不要传帖子链接、用户主页链接、post_id、user_id 或 page_token 作为 keyword。"New value: +"微博帖子搜索词，可传关键词或短语；不要传帖子链接、用户主页链接、post_id、user_id 或 page_token。"

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"
+]

Changed1 schema field changedAug 14, 2026

changedInput schema / properties / keyword / description

Previous value: -"微博帖子搜索关键词；不要传帖子链接、用户主页链接或分页 token。"New value: +"微博帖子搜索关键词；自然语言关键词可传品牌名、话题、人物名、内容需求或研究主题；不要传帖子链接、用户主页链接、post_id、user_id 或 page_token 作为 keyword。"

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

A4.7/5.0

Behavior5/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 and dynamic-world behavior is covered. The description adds useful behavioral context beyond annotations by stating that pagination is supported, and the detailed page_token handling rules further clarify expected usage. No contradiction exists.

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 compact: three sentences, each earning its place. The primary action is front-loaded, usage guidance follows, and pagination is mentioned last without any verbose filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search tool with an output schema, annotations, and detailed parameter schemas, the description is fully adequate. It tells the agent what the tool does, when to use it, when to use alternatives, and that pagination is available, leaving no critical gap.

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 fully documents both parameters. The main description adds no new parameter-level meaning beyond saying pagination is supported; the keyword and page_token nuances are already captured in the schema.

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 opens with '按搜索词搜索微博帖子' (search Weibo posts by search term), a specific verb and resource. It then explicitly contrasts itself with post-specific and user-specific tools, so an agent can distinguish it from the many sibling tools.

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 states plainly to use this tool when the user wants to find posts by keyword or phrase, and gives explicit exclusion conditions: use the corresponding post tools when a post link or post_id is available, and user tools when a profile link or user_id is available. It also mentions pagination support with page_token.

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?