Skip to main content
Glama
etherwindy

Bangumi MCP

by etherwindy

get_my_episode_collections

Read-onlyIdempotent

Retrieve your episode collections for a given anime or manga subject, filterable by episode type and paginated.

Instructions

获取当前用户剧集收藏信息列表

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subject_idYes条目ID
paramsNo可选参数,包含以下字段:

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false. Description adds no further behavioral details but does not contradict. Transparency is adequate given annotations.

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?

Description is a single concise sentence that front-loads the purpose. It earns its place but could be slightly more informative.

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?

Given output schema exists and annotations cover safety, description is minimally complete. However, it does not explain the concept of episode collections or the output format, but schema likely compensates.

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 baseline is 3. Description adds no additional meaning beyond what schema provides.

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?

Description clearly states verb 'get' and resource 'current user's episode collection list'. It is specific and distinguishes from sibling like get_my_episode_collection_info, though not explicitly stated.

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?

No usage guidance provided in description. Does not mention when to use this vs alternatives, such as get_my_episode_collection_info for a single entry or get_user_episode_collections for other users.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/etherwindy/Bangumi-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server