Skip to main content
Glama

delete_qzone_msg

Destructive

Deletes a QQ Zone post by tid, using the identifier returned by get_qzone_msg_list; requires access or management permission for that post.

Instructions

删除一条说说(QQ 空间,按 tid) tid 来自 get_qzone_msg_list;操作需有该说说的访问或管理权限。

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

Input Schema

NameRequiredDescriptionDefault
tidYes说说 tid(来自 get_qzone_msg_list / send_qzone_msg)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the dangerous nature is known; the description adds beyond that by disclosing the permission requirement (access or management rights on the specific post). It does not state whether deletion is permanent, what error occurs when permission is missing, or rate-limit behavior, so it stops short of full transparency.

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?

The action and resource are front-loaded, followed by the identifier source and the permission prerequisite in a compact single passage with no filler. Every clause carries information an agent needs before calling.

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 one-parameter destructive tool with annotations covering the safety profile and no output schema, the description covers action, identifier provenance, and authorization. The remaining gap is the outcome of failure or irreversibility, which is minor given the destructiveHint annotation.

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 coverage is 100% and the single tid parameter is already documented in the schema, including its provenance. The description repeats that provenance ('tid 来自 get_qzone_msg_list') without adding format, length, or example details, so it earns the baseline rather than more.

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 states a specific verb and resource ('删除一条说说', i.e. delete one Qzone post) and identifies the identifier ('按 tid'), which cleanly distinguishes it from the generic delete_msg and comment/reply deletion siblings. It falls short of a 5 only because it does not name which sibling to use for adjacent objects.

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?

It specifies where the required tid must come from ('来自 get_qzone_msg_list') and states a prerequisite (access or management permission on that post), which gives useful context for when the tool applies. However, it gives no explicit when-not guidance or alternatives for deleting comments, replies, or other Qzone objects.

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