Skip to main content
Glama

get_group_album_list

Read-only

Fetches the photo album list for a given QQ group ID, returning basic details for each album.

Instructions

get_group_album_list 将 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_album_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds return-shape information (an array of albums with basic info per item), which is valuable because there is no output schema, but it says nothing about pagination, ordering, or what happens when the group has no albums or the account lacks access.

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?

Two short sentences with no padding, which is appropriately sized. However, structure is slightly off: the leading sentence is a parameter-usage note rather than a statement of purpose, so the reader has to reach the second sentence to learn what gets returned.

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 read tool the description covers the essential call mechanics (accessible group number) and the return shape, which is adequate. It falls short on routing: with a sibling that appears to do the same thing (get_qun_album_list), the description should give the agent a reason to choose one over the other.

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 100% and there is only one required parameter, so the baseline is 3. The description does add a bit of meaning beyond the schema's bare label "群号" by insisting the value must be a group number the current account can access, but it gives no format or type guidance beyond that.

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 says it returns an array of group albums ("群相册列表数组,每项为一个相册的基本信息"), which confirms the resource, but the first sentence focuses on how to fill in the parameter rather than stating what the tool does. It does nothing to distinguish this tool from near-duplicate siblings such as get_qun_album_list or get_group_album_media_list, so an agent cannot tell them apart from the description alone.

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 usage constraint given is implicit: group_id must be a group the current account can access. There is no indication of when to pick this tool over get_qun_album_list, or over get_group_album_media_list when album contents are wanted, and no exclusions or prerequisites beyond accessibility are stated.

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