Skip to main content
Glama

get_group_album_media_list

Read-only

Fetches images and videos from a QQ group album, returning media details and a next-page cursor for pagination.

Instructions

get_group_album_media_list album_id 来自 get_group_album_list;lloc 或视频 id、batch_id 来自 get_group_album_media_list。替换群号及对应资源标识。 下一页传回 nextAttachInfo。 Returns: 相册图片/视频列表及下一页分页游标;视频项包含 id、url、cover、尺寸、时长和多规格地址。

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

Input Schema

NameRequiredDescriptionDefault
album_idYes
group_idYes群号
attach_infoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered; the description goes further and discloses the return payload (image/video items plus a next-page cursor, with video items carrying id, url, cover, size, duration and multi-bitrate addresses). It omits any permission or rate-limit notes, but for a read tool this is a meaningful addition beyond the annotations.

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 prerequisite, but the mixed Chinese/English phrasing plus the leftover reference to parameters that do not exist make it read like a stitched-together fragment rather than a polished definition. Every sentence roughly earns its place, yet the noise reduces clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three parameters, no output schema and no nested objects, the definition supplies the missing pieces an agent needs: where album_id comes from, how pagination works, and what the response contains. The only real gap is the unexplained stray identifiers, not missing operational information.

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 only 33%, and the description does compensate partially by explaining that album_id comes from get_group_album_list and that the cursor is passed back via attach_info (the returned nextAttachInfo). However, it also references 'lloc', 'video id' and 'batch_id', which are not parameters of this tool, introducing confusion rather than clarifying the actual schema.

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 verb+resource are explicit (fetch a group album's media list) and the definition names get_group_album_list as the tool that produces album_id, which separates it from the sibling that lists albums. The self-referential sentence fragment about 'lloc 或视频 id、batch_id 来自 get_group_album_media_list' muddies an otherwise clear purpose, since those identifiers are not inputs of this tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete provenance for the required input (album_id from get_group_album_list) and states the pagination protocol: pass the returned nextAttachInfo back on the next call. It stops short of stating when-not-to-use cases or naming non-album alternatives, but the call sequence guidance is unusually actionable.

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