Bangumi MCP

get_user_person_collection_info

Read-onlyIdempotent

Retrieve a user's collection status for a specific person on Bangumi. Input username and person ID to get collection details.

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>",
      "person_id": "<person_id>"
    },
    "name": "get_user_person_collection_info"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes	用户名/ID
`person_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

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, making the behavior clear. The description adds no additional behavioral context beyond what the annotations provide. With annotations present, a score of 3 is appropriate as the description does not add extra transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no redundant information. It is appropriately sized for the tool's simplicity and front-loaded with the essential action. Every word earns its place.

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?

Given the presence of an output schema and annotations, the description is minimally complete. However, it lacks context on how this tool differs from siblings like get_user_person_collections, or any edge cases. For a simple read operation, it is adequate but not thorough.

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?

The input schema has 100% description coverage for both parameters. The description '获取用户指定人物收藏信息' does not add extra meaning beyond the schema's property descriptions. Baseline 3 is justified since the schema covers parameter semantics adequately.

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 clearly states the action (获取用户指定人物收藏信息 - get user's specified person collection info) and resource. However, it does not explicitly differentiate from sibling tools like get_user_person_collections, which likely lists collections for a user. The name implies specificity but without explicit distinction.

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 alternatives. There is no mention of when to choose this over get_user_person_collections or when not to use it. The description simply states the function without context for selection.

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

Deploy Server