Skip to main content
Glama

comment_qzone

Comments on QQ Zone posts or replies to specific comments using a post ID; normal comments can include images, while threaded replies accept text only.

Instructions

评论说说或回复指定评论(普通评论支持带图,楼中楼仅支持文字) tid 来自 get_qzone_msg_list;操作需有该说说的访问或管理权限。 Rules: all or none of: comment_id, comment_uin; all or none of: reply_uin, reply_name; reply_uin/reply_name require comment_id/comment_uin; images are not supported for comment replies; comment_id, reply_name and reply content must not be blank; comment_uin and reply_uin must be safe integers.

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": {
      "tid": "<tid>",
      "content": "<content>"
    },
    "name": "comment_qzone"
  }
}

Input Schema

NameRequiredDescriptionDefault
tidYes说说 tid
imagesNo图片数组(可选),支持 file:// http:// base64://;自动上传
contentYes评论内容
reply_uinNo楼中楼中要回复的用户 QQ 号,与 reply_name 同时提供,需指定父评论
comment_idNo一级父评论 ID,与 comment_uin 同时提供;编号 0 有效,不能传二级回复自身的 ID
reply_nameNo要回复的用户昵称,来自评论详情的 name;与 reply_uin 同时提供
target_uinNo说说所属 QQ 号,省略则为机器人自己
comment_uinNo一级父评论作者 QQ 号,与 comment_id 同时提供;不是说说所属账号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses a permission requirement, the image-capability difference between top-level and nested comments, and a set of cross-parameter invariants (all-or-none pairing of comment_id/comment_uin and reply_uin/reply_name, ordering dependency, non-blank requirements, safe-integer requirement for UINs). These constraints materially change how the tool must be invoked and are not derivable from the annotations.

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 purpose sentence and the tid/permission note are front-loaded, and the Rules block is compactly enumerated so each constraint is scannable. A few rules restate schema constraints already enforced by minLength/required, which is mild redundancy but useful as a single checklist.

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 an 8-parameter mutation with no output schema, the definition covers permissions, mode selection, image limits, and all cross-parameter constraints — everything needed to build a valid call. The remaining gap is return behavior: with no output schema, the description never says what a successful comment produces (e.g., the new comment_id), which an agent would need for follow-up operations like replies or deletion.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns above that by adding cross-field semantics the schema cannot express — that comment_id/comment_uin must be supplied together, that reply_uin/reply_name require a parent comment, and that images are rejected on replies. It does not elaborate on target_uin's default (robot self) or on the format of image URIs, which the schema already covers.

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 uses a specific verb+resource pair ('评论说说' / '回复指定评论') and explicitly distinguishes the two modes: top-level comment (image-capable) vs. nested reply (text-only). It also pins the source of 'tid' to get_qzone_msg_list. It stops short of naming a sibling it is not (e.g., comment_qzone_public_feed), so an agent must infer which Qzone commenting surface this applies to.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a real precondition ('操作需有该说说的访问或管理权限') and tells the agent where tid must come from, which is the main gating condition for calling it. It also implies when to use the reply path (must supply a parent comment). It does not say when to prefer a sibling commenting tool instead, so the alternative-selection guidance is incomplete.

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