SocialDataX 微博 Weibo MCP

weibo_get_post_comments_by_post_id

Read-only

根据 post_id 获取微博帖子一级评论，支持 page_token 翻页。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`post_id`	Yes	微博帖子长 ID；可从搜索、详情、转发或用户帖子列表结果中的 post_id 复用。
`sort_type`	No	微博一级评论排序方式。hot 表示默认热门评论流；time_descending 表示当前可返回范围内最新评论优先。默认 hot。继续翻页时必须与上一页返回 next_page_token 所属的 sort_type 保持一致。	hot
`page_token`	No	微博评论分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一帖子、同一 sort_type 的评论分页链路，不能跨帖子或排序方式复用。

Output Schema

TableJSON Schema

Name	Required	Description
`items`	Yes	当前页一级评论列表。
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`comment_count`	Yes	总评论数，含一级评论与回复；不是当前页 items 数量；不可用时为 null。
`next_page_token`	Yes	下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回；next_page_token 只能用于同一能力和同一分页链路；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 11, 2026

addedOutput schema / properties / items / items / properties / fan_badge

Added value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "fan_level": {
+          "description": "微博粉丝徽章等级，为正整数；不要与微博会员等级混淆。",
+          "minimum": 1,
+          "type": "integer"
+        },
+        "fan_type": {
+          "description": "微博粉丝类型：iron 表示铁粉，gold 表示金粉，diamond 表示钻粉。",
+          "enum": [
+            "iron",
+            "gold",
+            "diamond"
+          ],
+          "type": "string"
+        },
+        "icon_url": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "粉丝徽章图标链接；不可用时为 null。"
+        }
+      },
+      "required": [
+        "fan_type",
+        "fan_level",
+        "icon_url"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "评论作者相对于当前帖子作者的粉丝徽章；当前评论未展示徽章或信息无法确认时为 null，不代表该用户一定不是帖子作者的粉丝。"
+}

removedOutput schema / properties / items / items / properties / is_top_fan

Removed value: -{
-  "default": false,
-  "description": "该评论是否展示针对该帖作者的微博铁粉标识。",
-  "type": "boolean"
-}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "post_id",
-  "comment_id",
-  "content",
-  "publish_time",
-  "like_count",
-  "has_replies",
-  "ip_location",
-  "image_urls",
-  "author"
-]New value: +[
+  "fan_badge",
+  "post_id",
+  "comment_id",
+  "content",
+  "publish_time",
+  "like_count",
+  "has_replies",
+  "ip_location",
+  "image_urls",
+  "author"
+]

Changed1 schema field changedSep 9, 2026

addedOutput schema / properties / items / items / properties / is_top_fan

Added value: +{
+  "default": false,
+  "description": "该评论是否展示针对该帖作者的微博铁粉标识。",
+  "type": "boolean"
+}

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",
-  "comment_count"
-]New value: +[
+  "items",
+  "next_page_token",
+  "comment_count",
+  "points"
+]

Changed2 schema fields changedJul 16, 2026

addedOutput schema / properties / items / items / properties / image_urls

Added value: +{
+  "description": "评论图片链接列表；无图片时为空数组。",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "post_id",
-  "comment_id",
-  "content",
-  "publish_time",
-  "like_count",
-  "has_replies",
-  "ip_location",
-  "author"
-]New value: +[
+  "post_id",
+  "comment_id",
+  "content",
+  "publish_time",
+  "like_count",
+  "has_replies",
+  "ip_location",
+  "image_urls",
+  "author"
+]

Changed2 schema fields changedJul 9, 2026

addedOutput schema / properties / items / items / properties / ip_location

Added value: +{
+  "description": "评论发布时的 IP 属地；没有时为空字符串。",
+  "type": "string"
+}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "post_id",
-  "comment_id",
-  "content",
-  "publish_time",
-  "like_count",
-  "has_replies",
-  "author"
-]New value: +[
+  "post_id",
+  "comment_id",
+  "content",
+  "publish_time",
+  "like_count",
+  "has_replies",
+  "ip_location",
+  "author"
+]

Changed2 schema fields changedJun 24, 2026

changedInput schema / properties / page_token / description

Previous value: -"微博评论分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一帖子评论分页链路，不能跨帖子复用。"New value: +"微博评论分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一帖子、同一 sort_type 的评论分页链路，不能跨帖子或排序方式复用。"

addedInput schema / properties / sort_type

Added value: +{
+  "default": "hot",
+  "description": "微博一级评论排序方式。hot 表示默认热门评论流；time_descending 表示当前可返回范围内最新评论优先。默认 hot。继续翻页时必须与上一页返回 next_page_token 所属的 sort_type 保持一致。",
+  "enum": [
+    "hot",
+    "time_descending"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedJun 22, 2026

addedOutput schema / properties / comment_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "总评论数，含一级评论与回复；不是当前页 items 数量；不可用时为 null。"
+}

changedOutput schema / required

Previous value: -[
-  "items",
-  "next_page_token"
-]New value: +[
+  "items",
+  "next_page_token",
+  "comment_count"
+]

First observedJun 22, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations provide readOnlyHint and openWorldHint, so the safety profile is covered. The description adds that it returns '一级评论' (first-level comments only) and supports pagination, which is useful scope info. But it does not disclose rate limits, ordering defaults beyond what schema says, or response characteristics.

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 tight sentence that front-loads the core action (get comments by post_id) and appends the pagination capability. No wasted words.

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?

With annotations covering safety and a fully documented schema plus an output schema, the description needs only to state scope and the first-level-comments constraint, which it does. It could mention behavior on invalid post_ids or sorting defaults, but that is minor given the rich schema.

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 parameters are fully documented in the schema (including sort_type enum semantics and page_token immutability rules). The description adds no parameter detail beyond what the schema provides, so the baseline 3 applies.

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?

Clear verb+resource: retrieves first-level comments for a given Weibo post, keyed by post_id, with page_token pagination noted. It distinguishes itself implicitly from siblings like weibo_get_post_comment_replies_by_comment_id (replies) and weibo_get_post_comments_by_post_url (URL variant), but doesn't explicitly name them.

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 usage (fetch top-level comments given a post_id, paginate with page_token). However, it does not explicitly state when to use this tool vs. the URL-based variant or the replies tool, leaving the agent to infer selection from the tool name alone.

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?