Bangumi MCP

get_user_collection_info

Read-onlyIdempotent

Retrieve a specific user's collection information for an anime or manga entry, including their rating, status, and personal tags.

Instructions

获取用户指定条目信息

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": {
      "username": "<username>",
      "subject_id": "<subject_id>"
    },
    "name": "get_user_collection_info"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes	用户名/ID
`subject_id`	Yes	条目ID

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 18, 2026

TDQS

C2.3/5.0

Behavior2/5

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

The description adds no behavioral information beyond the annotations, which already indicate read-only, idempotent, and non-destructive behavior. It does not explain what data is returned or any other behavior.

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?

The description is extremely short, which is concise but at the expense of informativeness. It is not a well-structured explanation; it is simply a phrase.

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

Completeness2/5

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

The description does not provide sufficient context for the tool's purpose or output, despite having siblings and an output schema. It fails to explain what 'collection info' encompasses or how the result is structured.

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 100%, so the schema already describes the parameters. The description does not add any additional meaning or context beyond the schema's parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '获取用户指定条目信息' translates to 'Get user specified item information', which is vague and does not specify what type of collection or item. It does not distinguish from sibling tools like get_user_character_collection_info or get_user_person_collection_info, making it unclear when to use 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 Guidelines2/5

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

No guidance is provided on when to use this tool versus other similar collection info tools. The description lacks any context about prerequisites or alternative tools.

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

Deploy Server