Skip to main content
Glama

comment_qzone_public_feed

Comments on a Qzone public feed using a feed entry returned by get_qzone_public_feeds and text or rich content, avoiding comments built from stale tids.

Instructions

评论推荐动态,支持文本或上游富文本条目 feed 必须原样取自 get_qzone_public_feeds 的 feeds 数组,不能用旧说说 tid 拼造;示例中的占位字段须整体替换。 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>",
      "content": "<content>"
    },
    "name": "comment_qzone_public_feed"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the description adds rather than repeats: it discloses that the call returns the upstream comment result including the new comment and that unknown fields are preserved. It still omits failure modes and permission requirements, so it is not fully transparent.

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 and front-loads the action and the critical feed-sourcing constraint before the return note. It is a single run-on block mixing operation, constraints, and return values, but each clause carries information that is not pure filler.

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?

For a two-parameter write tool with no output schema, the definition covers the action, the mandatory provenance of the feed object, the accepted content shapes, and the return payload. Remaining gaps (error behavior, ownership constraints, duplicate-comment handling) are modest given the annotations already signal an open-world, non-destructive write.

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 both parameters are already documented, including that content is a string or RichItem array and is not a OneBot message segment. The description restates the feed provenance rule from get_qzone_public_feeds, which is useful emphasis, but adds no new syntax or format meaning beyond the schema.

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 verb and resource ('评论推荐动态' = comment on a recommended feed) and notes it accepts text or upstream rich-text items, which is enough to distinguish it from read-oriented siblings like get_qzone_public_feed_detail. It does not explicitly differentiate it from reply_qzone_public_feed or forward_qzone_public_feed, so a sibling-level distinction is only partial.

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 a strong precondition: the feed must be copied verbatim from get_qzone_public_feeds' feeds array and must not be fabricated from an old tid, which is genuinely useful routing context. However, it never says when to prefer this over reply_qzone_public_feed or forward_qzone_public_feed, and gives no exclusion conditions.

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