Skip to main content
Glama

get_qun_album_list

Read-only

Retrieves a QQ group album list with pagination; pass the previous page's attach_info to fetch subsequent pages and use has_more to detect the end.

Instructions

get_qun_album_list 后续页原样传回上一页的 attach_info;has_more=false 表示结束。 Returns: NapCat 风格的相册列表封套:{album_list, attach_info, has_more}。

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_qun_album_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes群号
attach_infoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower, and the description still adds real behavior: the pagination protocol via attach_info and the has_more termination signal. It also discloses the exact response envelope, which is valuable given there is no output schema. It stops short of mentioning permissions or rate limits.

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 dense sentences with no filler, and each clause carries distinct information (pagination rule, termination condition, return shape). The weakness is ordering: it leads with the continuation-page mechanic instead of stating the tool's core purpose first.

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 two-parameter read tool with no output schema, the description does cover the return envelope and pagination, which are the main risks. However, it leaves the basic question of what the tool retrieves and how it relates to its near-identical sibling get_group_album_list unanswered, which is a meaningful gap for selection.

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

Parameters4/5

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

Schema coverage is 50% and attach_info has no schema description at all, but the description compensates by explaining that it is an opaque cursor copied verbatim from the prior response. group_id is left to the schema's brief '群号' label, so coverage is good rather than complete.

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 never states plainly that this tool lists a group's albums; the resource is only inferable from the tool name and the phrase '相册列表封套' in the return note. It also fails to distinguish itself from the sibling get_group_album_list, which by name alone appears to serve the same resource, so an agent cannot tell the two apart from this text.

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 does give one concrete procedural rule: on subsequent pages, pass back the previous page's attach_info verbatim, and stop when has_more=false. What is missing is when to choose this tool at all versus get_group_album_list or get_group_album_media_list, and there are no stated prerequisites or exclusions.

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