Skip to main content
Glama
Sign In
JMComic AI

JMComic AI

by hect0x7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

browse_favorite_albums

Browse a logged-in account's favorite albums by folder, page, and sort order, returning lightweight summaries with IDs, titles, tags, and cover URLs.

Instructions

分页浏览已登录账户的收藏，返回轻量本子摘要。

参数: folder_id: 收藏夹 ID，"0" 表示全部收藏（默认值："0"）。 page: 页码，从 1 开始（默认值：1）。 order_by: 排序方式，favorite_time 按收藏时间、update_time 按更新时间 （默认值：favorite_time）。 username: HTML 客户端仅配置 Cookie（未设置 auth.username）时必须提供用户名； 通过 login 登录或配置顶层 auth 后可省略。API 客户端忽略此参数，始终查询当前登录账户。

返回: albums: 本子摘要列表，包含 id、title、tags、cover_url。 total_count: 收藏总数。 page: 当前页码。 folder_id: 查询的收藏夹 ID。 error: 页码、收藏夹 ID 或排序参数无效时的错误信息（可选）。

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": "browse_favorite_albums"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
order_byNofavorite_time
usernameNo
folder_idNo0

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses pagination, the read-only nature of browsing favorites, the auth-dependent behavior of username, and an error field returned for invalid page/folder/order values. It omits rate limits, what the account scoping means for shared or public content, and any indication of ordering stability across pages.

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 description is front-loaded with a purpose sentence and then cleanly sectioned into parameters and returns, with no filler. The returns block duplicates information that a separate output schema already provides, which is mild redundancy rather than noise.

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?

For a four-parameter read tool with an output schema, the agent has everything needed to call it: every parameter is explained, defaults are stated, the enum for order_by is supplied, auth conditions are described, and error behavior is noted. The only gap is guidance on how to obtain a valid folder_id, which would require pointing at get_favorite_folders.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must do all the work, and it does: every one of the four parameters is given meaning, defaults, and semantics beyond the bare schema types (folder_id '0' means all, page is 1-based, order_by accepts favorite_time/update_time as an enum not present in the schema, username's conditional requirement).

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 opening sentence names a specific verb and resource ('分页浏览已登录账户的收藏') plus the returned shape ('轻量本子摘要'), which separates it from the general browse_albums sibling. It never explicitly contrasts with browse_albums or get_favorite_folders, so the differentiation is implied by the word '收藏' rather than stated.

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?

Useful conditional guidance exists for the username parameter (required only for HTML cookie clients without auth.username, ignored by API clients). However, there is no explicit when-to-use versus alternatives guidance, such as telling the agent to call get_favorite_folders first to obtain a folder_id or when to prefer browse_albums.

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