Skip to main content
Glama

delete_qzone_public_reply

Destructive

Deletes a reply under a comment on a QQ Zone public feed using the full original feed, comment, and reply objects; requires permission.

Instructions

删除推荐动态评论下的一条回复(需有权限) feed 必须原样取自 get_qzone_public_feeds 的 feeds 数组,不能用旧说说 tid 拼造;示例中的占位字段须整体替换。 comment 可取 get_qzone_public_feed_detail 返回的 feed.feed.cell_comment.comments,或后续评论页;保留完整对象。 reply 使用该评论下的完整回复对象。 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>",
      "reply": "<reply>"
    },
    "name": "delete_qzone_public_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYesget_qzone_public_feeds 返回的完整 feeds 条目,保留所有原始 cell 字段
replyYes评论或回复页返回的完整回复对象,保留 user 等原始字段
commentYes详情或评论页返回的完整评论对象,保留 user 等原始字段

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds two things beyond them: the operation requires sufficient permissions, and the return is the upstream delete result with unknown fields preserved. It does not describe failure modes or irreversibility, but the added context is real.

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?

Dense and front-loaded: the delete action and permission caveat come first, then per-parameter provenance, then the return note. Every sentence carries operational information, though the placeholder-substitution remark is closer to boilerplate than the rest.

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 destructive, three-object tool with no output schema, the description covers prerequisites, parameter sourcing, permission requirements, and the return shape. The main residual gap is what happens on partial or unauthorized deletion, but nothing essential to invoking it correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning: the feed object must not be fabricated from an old tid, and placeholder fields in the example must be substituted wholesale. It also clarifies that objects must be passed through intact rather than reduced to IDs, which the schema only hints at.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

States a specific verb and resource at the exact granularity needed: deleting a single reply under a comment on a recommended feed, with a permission caveat. This distinguishes it from delete_qzone_public_comment, which removes a comment rather than a reply, without the agent having to open either schema.

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?

Gives an explicit provenance chain: feed must be taken verbatim from get_qzone_public_feeds, comment from get_qzone_public_feed_detail's feed.feed.cell_comment.comments or a later comment page, and reply from that comment's replies. That is strong when-and-how guidance naming the prerequisite tools, though it does not state when to prefer a sibling delete tool instead.

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