Skip to main content
Glama

get_group_member_list

Read-only

Retrieves the member list for a specified QQ group by group ID, with an option to bypass cached results. Use it to inspect group participants for moderation or member management.

Instructions

获取群成员列表 将 group_id 替换为当前账号可访问的群号。 Returns: 群成员信息对象数组。

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

Input Schema

NameRequiredDescriptionDefault
group_idYes群号
no_cacheNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the return shape ('array of group member info objects'), which is genuinely useful given there is no output schema, but it says nothing about result size, ordering, or pagination for what can be a very large member list.

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 sentences with the purpose front-loaded and no filler. The placeholder-style 'replace group_id with…' phrasing is slightly boilerplate but still earns its place as an access constraint.

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 simple two-parameter read tool with no output schema, the definition covers purpose, access precondition, and return type. It is still incomplete on the cache toggle and on any limits around large member lists, which matter for correct invocation.

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 50%: group_id is documented as '群号' and no_cache is undocumented in both schema and description. The description partially compensates by clarifying that group_id must be a group the current account can access, but the caching flag remains unexplained.

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?

States a specific verb and resource: retrieve the group member list. An agent can distinguish it from get_group_member_info by the singular/plural resource naming, though the description never explicitly contrasts the two.

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?

The only guidance is 'replace group_id with a group number accessible to the current account', which is a parameter-filling instruction and an access precondition rather than a when-to-use rule. There is no indication of when to prefer this over get_group_member_info (single member) or other group list 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