Skip to main content
Glama

qzone_delete_comment

Destructive

Remove a comment from a Qzone post (说说) by specifying the post ID, comment ID, and commenter UIN. Use it to delete comments on your own posts or your own comments elsewhere.

Instructions

Delete a comment under a 说说 (any comment on your own 说说, or your own comment elsewhere).

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>",
      "comment_id": "<comment_id>",
      "comment_uin": "<comment_uin>"
    },
    "name": "qzone_delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
tidYes说说 tid
uinNoAuthor of the 说说 (default: you)
comment_idYesComment id (from get_qzone_msg_detail)
comment_uinYesWho wrote the comment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the risk profile is known from structured data. The description adds a real behavioral constraint beyond that — the ownership/eligibility rule — but says nothing about irreversibility, error behavior on ineligible comments, or result shape. Useful addition, but modest against an already-covered safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the action front-loaded and the eligibility rule immediately after. No filler, no redundancy, and nothing important is deferred.

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 4-parameter destructive delete with full schema coverage and no output schema, the essentials are present: what it deletes, whose comments are eligible, and where the comment id comes from (via the schema). Only the irreversibility of the deletion and the public-feed alternative are left unstated.

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 description coverage is 100% and every parameter (tid, uin, comment_id, comment_uin) carries its own description, including the useful pointer that comment_id comes from get_qzone_msg_detail. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

Uses a specific verb+resource ('Delete a comment under a 说说') and adds a scope parenthetical clarifying which comments are eligible (any comment on your own 说说, or your own comment elsewhere). It does not name the sibling delete_qzone_public_comment, so sibling differentiation is implied by scope rather than stated, keeping it below a 5.

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?

The parenthetical effectively encodes an eligibility precondition — the comment must be on your own 说说 or be your own comment — which tells the agent when this tool will succeed. It stops short of explicitly routing to the public-feed/comment siblings for comments in public feeds, so guidance is implied rather than enumerated.

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