Skip to main content
Glama

delete_msg

Destructive

Use a real message_id from a message event or send result to recall a QQ message; negative IDs work when the message remains queryable in the current account's message store.

Instructions

撤回消息 使用消息事件或发送结果中的真实 message_id,负值合法;消息须在当前账号的消息存储中可查询。

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

Input Schema

NameRequiredDescriptionDefault
message_idYes

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 readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the agent knows this is an irreversible mutating action; the description adds a useful scoping constraint — the message must be queryable in the current account's message store. It does not say whether there is a time window for recall, what the failure response looks like, or what permissions are required, which is a real gap for a destructive operation.

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?

Two short clauses, verb-first and front-loaded, with the ID-sourcing rule immediately after the action. Nothing is padded; the only weakness is that the densely packed semicolon clauses read as one run-on rather than clearly separated rules.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter destructive tool with no output schema, the description covers the action and the ID contract adequately. It is thin on outcome behavior — nothing about recall limits, partial failure, or what the caller receives on error — which matters for a delete that may be time-bounded on some platforms.

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 description coverage is 0%, so the description must carry parameter meaning, and it does: it explains where a valid message_id comes from (message events or send results), that negative values are legal, and that the message must be reachable in the account's store. This meaningfully resolves the schema's otherwise unexplained `not: {const: 0}` constraint. It does not address why the field also accepts a string type.

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?

"撤回消息" gives a specific verb (recall/withdraw) plus a specific resource (a chat message), so the agent knows it operates on messages rather than on friends, files, or Qzone posts. It does not explicitly distinguish itself from sibling delete tools such as delete_essence_msg or delete_qzone_msg, so it stops short of full sibling differentiation.

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 description supplies a usable precondition (the ID must come from a message event or a send result, and the message must exist in the current account's store), which effectively tells the agent when the call will succeed. It gives no guidance on when to prefer this tool over the other delete_* siblings, and no exclusions or failure-condition handling.

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