Skip to main content
Glama

reply_qzone_public_feed

Sends a reply to a comment or nested reply on a QQ Zone public feed using the original feed and comment data.

Instructions

回复推荐动态的评论或其中某条回复 feed 必须原样取自 get_qzone_public_feeds 的 feeds 数组,不能用旧说说 tid 拼造;示例中的占位字段须整体替换。 comment 可取 get_qzone_public_feed_detail 返回的 feed.feed.cell_comment.comments,或后续评论页;保留完整对象。 Returns: 上游回复结果,包含新回复,保留未知字段。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "feed": "<feed>",
      "comment": "<comment>",
      "content": "<content>"
    },
    "name": "reply_qzone_public_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYesget_qzone_public_feeds 返回的完整 feeds 条目,保留所有原始 cell 字段
replyNo评论或回复页返回的完整回复对象,保留 user 等原始字段
commentYes详情或评论页返回的完整评论对象,保留 user 等原始字段
contentYes非空文本,或非空上游 RichItem 对象数组;字符串始终原样发送,富文本请直接传对象数组,不是 OneBot 消息段

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already disclose that this is a non-read-only, open-world, non-destructive operation. The description adds useful behavioral constraints beyond that: feed objects must be taken verbatim from upstream feeds, placeholder fields must be fully replaced, and returned unknown fields are preserved.

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?

The description is dense but front-loads the core action and then gives source and return-value constraints. Every sentence is relevant, though the reference to placeholder fields in examples is slightly opaque without the examples.

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

Completeness3/5

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

For a nested-object write tool with no output schema, the description usefully describes the return value and upstream source requirements. It remains incomplete on the distinction between the reply and comment parameters and on when this tool should be chosen over sibling comment/reply tools.

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 coverage is 100%, so the baseline is 3. The description adds meaningful provenance rules for feed and comment, including that feed must not be fabricated from an old tid, but it does not explain the reply parameter and adds little beyond the schema for content.

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 states a specific action: replying to a comment or nested reply on a recommended feed, and ties the inputs to required upstream sources. It is not fully sibling-differentiating because it never explicitly contrasts with comment_qzone_public_feed or clarifies top-level comment vs. reply semantics.

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?

It gives concrete usage constraints by requiring feed to come from get_qzone_public_feeds and comment from get_qzone_public_feed_detail or later comment pages. However, it gives no explicit when-to-use guidance against sibling comment/reply tools and does not explain when to use the reply parameter.

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

Deploy Server

Other Tools