Skip to main content
Glama

delete_group_file_folder

Destructive

Deletes a specified QQ group folder by group ID and folder ID, enabling cleanup of group file resources after confirmation.

Instructions

删除群文件夹 会删除指定群文件夹,确认资源后调用。

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": {
      "group_id": "<group_id>",
      "folder_id": "<folder_id>"
    },
    "name": "delete_group_file_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes群号
folder_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is supplied structurally. The description adds only a confirmation caution, and does not disclose whether deletion is irreversible or whether contained files are removed with the folder. With annotations covering the core behavior, the modest addition earns a 3.

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

Conciseness3/5

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

It is short and front-loaded, which is good, but the second clause ('会删除指定群文件夹') is pure repetition of the first and the caution is tacked on without structure. Roughly half the text does no work.

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

Completeness2/5

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

For a destructive, open-world mutation with no output schema and a partially undocumented schema, the description omits critical facts: what happens to folder contents, whether the action is reversible, permission requirements, and the meaning of folder_id. It is too thin relative to the tool's risk.

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

Parameters2/5

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

Schema coverage is only 50%: group_id carries a '群号' description while folder_id has none. The description supplies no parameter meaning at all (no ID format, no source for folder_id), so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb and resource ('删除群文件夹' / delete group folder), so the basic action is identifiable. However, it does not differentiate this tool from the sibling 'delete_group_folder', nor from the file-level 'delete_group_file' set, leaving the agent unsure which delete variant applies. The second clause only restates the first.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'确认资源后调用' gives a minimal precondition (verify the target before calling), but there is no guidance on when to choose this over delete_group_folder or the other delete_* siblings, and no stated exclusions. The agent is left to infer selection from the tool name alone.

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