Skip to main content
Glama

delete_group_tag

Destructive

Removes a profile tag from a specified QQ group category; the current account must have management permissions.

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_class": "<group_class>",
      "name": "<name>"
    },
    "name": "delete_group_tag"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
group_classYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 destructive profile is covered structurally. The description adds the authorization requirement (management permission), which is useful behavioral context, but says nothing about reversibility, side effects, or what happens on failure.

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-loads the action, but the second clause ('替换实际群分类和标签') is a placeholder-substitution note that reads awkwardly and blurs with the purpose statement rather than clearly separating prerequisite from instruction.

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?

This is a destructive mutation with no output schema and zero parameter documentation, so the description carries the full burden and does not meet it. An agent still cannot tell what identifying format to pass or what the result of a successful removal looks like.

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 description coverage is 0%, so the schema documents neither parameter's meaning, and the description compensates only loosely by mapping 群分类/标签 to the two fields. It never clarifies that group_class is a numeric ID versus the string tag name, nor what formats are accepted.

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: remove a resource tag (资料标签) from a group category (群分类). That is concrete enough to distinguish it from the add_group_tag sibling without opening either schema, though it never names the counterpart explicitly.

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 supplies one real precondition — the current account must hold management permission — which is genuine when-to-use guidance. However, there is no statement of when to prefer this over alternatives or when not to call it, so usage remains only implied.

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