Skip to main content
Glama

SocialDataX 微博 Weibo MCP

by com.52choujiang
OverviewDiscussionsAdmin

weibo_get_post_comment_replies_by_comment_id

Read-only

根据 post_id 和一级评论 comment_id 获取微博评论回复；用户已提供完整合法的 ID 组合时直接使用；已有 post_id、帖子链接或分享文案但缺少必需 ID 时，调用对应一级评论工具获取同一条一级评论的 post_id 和 comment_id；缺少帖子定位信息时向用户索取；支持 page_token 翻页。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYes微博帖子长 ID；调用评论回复工具时必填，需与一级评论 comment_id 同时传入；用户已提供时直接使用，否则从一级评论结果 items[*].post_id 复用。
comment_idYes微博一级评论 ID；用户已提供时直接使用，否则可从一级评论结果 items[*].comment_id 复用；需与同一项 post_id 同时传入，不要传评论回复项的 comment_id。
page_tokenNo微博评论回复分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一帖子下同一一级评论的回复分页链路，不能跨帖子或评论复用。

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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: -[
-  "comment_id",
-  "content",
-  "publish_time",
-  "like_count",
-  "ip_location",
-  "image_urls",
-  "author"
-]New value: +[
+  "fan_badge",
+  "comment_id",
+  "content",
+  "publish_time",
+  "like_count",
+  "ip_location",
+  "image_urls",
+  "author"
+]
  2. Changed1 schema field changed
    • addedOutput schema / properties / items / items / properties / is_top_fan
      Added value: +{
+  "default": false,
+  "description": "该回复是否展示针对该帖作者的微博铁粉标识。",
+  "type": "boolean"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / comment_id / description
      Previous value: -"微博一级评论 ID；可从一级评论结果 items[*].comment_id 复用，用于获取该评论下的回复；需与同一项 post_id 同时传入，不要传评论回复项的 comment_id。"New value: +"微博一级评论 ID；用户已提供时直接使用，否则可从一级评论结果 items[*].comment_id 复用；需与同一项 post_id 同时传入，不要传评论回复项的 comment_id。"
    • changedInput schema / properties / post_id / description
      Previous value: -"微博帖子长 ID；调用评论回复工具时必填，需与一级评论 comment_id 同时传入；请从一级评论结果 items[*].post_id 复用，并与同一项 comment_id 一起传入。"New value: +"微博帖子长 ID；调用评论回复工具时必填，需与一级评论 comment_id 同时传入；用户已提供时直接使用，否则从一级评论结果 items[*].post_id 复用。"
  4. Changed2 schema fields changed
    • 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"
+]
  5. Changed2 schema fields changed
    • addedOutput schema / properties / items / items / properties / image_urls
      Added value: +{
+  "description": "评论回复图片链接列表；无图片时为空数组。",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
-  "comment_id",
-  "content",
-  "publish_time",
-  "like_count",
-  "ip_location",
-  "author"
-]New value: +[
+  "comment_id",
+  "content",
+  "publish_time",
+  "like_count",
+  "ip_location",
+  "image_urls",
+  "author"
+]
  6. Changed2 schema fields changed
    • addedOutput schema / properties / items / items / properties / ip_location
      Added value: +{
+  "description": "评论回复发布时的 IP 属地；没有时为空字符串。",
+  "type": "string"
+}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
-  "comment_id",
-  "content",
-  "publish_time",
-  "like_count",
-  "author"
-]New value: +[
+  "comment_id",
+  "content",
+  "publish_time",
+  "like_count",
+  "ip_location",
+  "author"
+]
  7. First observed

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=true already declare the safety and open-world profile. The description adds the id-sourcing workflow and pagination support, but pagination is fully repeated in the schema, so genuinely new behavioral context (auth needs, rate limits, what the reply objects contain) is thin. A 3 is appropriate given annotation coverage.

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?

Front-loaded with the core purpose, then the ID-sourcing and pagination clauses. It is a single dense semicolon-delimited sentence, slightly run-on, but every clause carries routing information and nothing is redundant.

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 explained, and the description covers purpose, ID prerequisites, alternative-tool routing, and pagination. It is essentially complete for this tool; only explicit sibling contrast and edge-case error behavior are absent.

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 page_token param carries very detailed opaque-token rules in the schema itself. The description adds no parameter syntax or format detail beyond the schema. 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: fetch Weibo comment replies keyed by post_id + first-level comment_id. It implies the distinction from sibling 'get first-level comments' tools by naming the workflow to obtain the IDs, but it never explicitly contrasts itself with weibo_get_post_comments_by_post_id. Clear purpose, partial sibling differentiation.

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?

Explicitly covers all three cases: use directly when a complete legal ID pair is present, call the corresponding first-level comment tool when only post_id/link/share text exists, and ask the user when post location info is missing. This is textbook when-to-use/when-not routing.

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