Skip to main content
Glama

qzone_board_delete

Destructive

Delete a QQ Zone message board post from your own board or one you wrote elsewhere by specifying the message ID and author QQ number.

Instructions

Delete a 留言板 message (on your own board, or one you wrote 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": {
      "message_id": "<message_id>",
      "author_uin": "<author_uin>"
    },
    "name": "qzone_board_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
uinNoQQ number whose 空间 to use (default: your own)
author_uinYesWho wrote it (from qzone_board_list)
message_idYes留言 id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, so the irreversible-write profile is structured data and needs no restating. The description adds the ownership/permission constraint, but says nothing about failure behavior when the caller lacks rights, nor whether the deletion is permanent or recoverable.

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?

One short sentence with the verb and resource front-loaded and no wasted phrasing. The scope qualifier is folded into a parenthetical efficiently, though the mixed-language token '留言板' slightly slows first-read comprehension.

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 three-parameter delete with full schema coverage and annotations that already declare destructiveness, the description supplies the one thing structured fields cannot: which messages are eligible for deletion. Only the error/permission-denied path is left unstated, a minor gap.

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%, including 'from qzone_board_list' for author_uin and the default for uin, so the schema carries parameter meaning. The description adds no format, id-syntax, or cross-parameter relationship beyond what the schema already states; 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?

Names a specific verb (Delete) plus the resource (a 留言板 message) and immediately scopes it: "on your own board, or one you wrote elsewhere." That distinguishes it from private-message deleters like delete_qzone_msg or delete_qzone_public_comment, though it relies on the reader knowing that 留言板 is a distinct surface.

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 implies an eligibility condition — you may delete only messages on your own board or ones you authored — which is real usage guidance. It does not state when to prefer a sibling such as delete_qzone_comment, nor what happens when neither condition holds, so the guidance is implied rather than explicit.

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