Skip to main content
Glama

delete_qzone_public_comment

Destructive

Deletes a QQ Zone recommended-feed comment using full feed and comment objects from the feed listing or comment page; requires permission.

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>"
    },
    "name": "delete_qzone_public_comment"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive=true, readOnly=false, openWorld=true, so the safety profile is covered. The description adds real context beyond that: a permission requirement, the prohibition on fabricating feed from an old tid, the mandate to preserve complete objects, and the shape of the return value with unknown fields 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 purpose and permission caveat are front-loaded, followed by parameter sourcing and the return note; every sentence carries operational meaning. It is dense but not padded, with only minor redundancy between the sourcing rules and the schema's own descriptions.

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 nested-object mutation with no output schema, the definition covers sourcing, permission, object fidelity, and return shape. What remains unstated is irreversibility and failure modes, which the destructive annotation only partially implies.

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

Parameters5/5

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

Schema coverage is already 100%, yet the description adds the crucial provenance rules that the schema cannot express: exactly which upstream call each object must be copied from and that placeholder fields must be fully replaced. This directly prevents the most likely invocation error for nested opaque objects.

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 and resource: delete one comment on a recommended feed, with an explicit permission precondition. It is clear about the target object type, though it never names the closest sibling (delete_qzone_public_reply) to draw the boundary between deleting a comment versus a reply.

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 concrete prerequisites and an explicit sourcing chain: feed must come verbatim from get_qzone_public_feeds' feeds array, and comment from get_qzone_public_feed_detail's feed.feed.cell_comment.comments or later comment pages. It does not state when to prefer this tool over the other deletion siblings, so the when-not side is missing.

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