Skip to main content
Glama

set_group_kick_members

Destructive

Remove multiple members from a QQ group by specifying the group ID and member QQ IDs; whether the action is allowed depends on the current account's permissions in that group.

Instructions

批量踢出群成员 替换群号和成员 QQ 号;操作是否允许取决于当前账号在该群的权限。

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

Input Schema

NameRequiredDescriptionDefault
user_idYes
group_idYes群号
reject_add_requestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 agent knows this is a consequential write. The description adds that execution is permission-gated, but it does not describe irreversibility, batch limits, what happens to kicked members, or how reject_add_request changes future joins.

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, front-loaded with the action. The phrase 替换群号和成员 QQ 号 is a slightly awkward documentation artifact, but overall there is little waste.

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 destructive three-parameter batch operation, the description gives the essential permission caveat and the batch scope, and annotations carry the destructive/open-world profile. It still leaves reject_add_request and batch limits unexplained, so an agent cannot fully predict behavior.

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?

The schema documents only group_id at 33% coverage. The description maps group_id and user_id to group number and member QQ numbers and signals that member IDs are batch, but it says nothing about reject_add_request or array limits.

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 uses the specific verb 批量踢出 (batch kick) with the resource 群成员 (group members), and the word 批量 signals the distinction from the singular sibling set_group_kick. It does not explicitly name the alternative, 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?

It notes that whether the operation is permitted depends on the current account's permissions in that group, which is a useful prerequisite. However, it gives no explicit when-to-use/when-not-to-use guidance versus set_group_kick, set_group_ban, or other sibling tools.

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