Skip to main content
Glama

get_collection_list

Read-only

Retrieves collection entries from a QQ account by category and count, returning items plus a bottom time cursor for pagination.

Instructions

获取收藏列表 Returns: 返回收藏条目、是否还有更多数据及底部时间游标。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_collection_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo最多返回的收藏数量
categoryNo收藏分类 ID;0 表示全部分类

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 useful behavioral context by stating the return payload contains entries, a has-more flag, and a bottom time cursor. It does not explain pagination mechanics or how the cursor is consumed, which is the main remaining gap.

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?

The definition is a single compact statement with the purpose front-loaded and the return shape appended. Nothing is wasted, though the brevity borders on under-specification rather than tight editing.

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?

With only two optional parameters and no output schema, the description covers the essentials, and the return-value note compensates for the missing output schema. However, it mentions a 'bottom time cursor' without explaining how to use it for pagination, and the input schema exposes no cursor parameter, leaving a real gap for a list tool.

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 description coverage is 100%, so the schema already documents 'count' (max 500, default 50) and 'category' (0 = all categories). The description adds no meaning beyond those fields, which is acceptable given the schema does the heavy lifting.

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 names a specific verb and resource ('获取收藏列表'), so an agent can immediately tell this retrieves the favorites/collection list. It does not distinguish itself from the many sibling list tools (get_flash_file_list, get_essence_msg_list, etc.), but the resource itself is unambiguous.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer usage purely from the tool name and the two parameter names.

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