Bangumi MCP

get_user_character_collection_info

Read-onlyIdempotent

Fetch a user's saved information about a specific anime character by providing their username and character ID.

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>",
      "character_id": "<character_id>"
    },
    "name": "get_user_character_collection_info"
  }
}

Input Schema

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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the tool is clearly a safe read operation. The description adds no further behavioral context (e.g., auth needs, rate limits, or data details). The output schema may cover return values, so no deduction.

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 exceptionally concise: a single, front-loaded phrase with no wasted words. Every word contributes to the purpose.

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 the tool's simplicity (2 simple params), presence of output schema, and robust annotations, the description is largely complete. It could mention return data nature, but the output schema fills that gap. The sibling context also helps disambiguate usage.

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 covers both parameters with descriptions ('用户名/ID', '角色ID'). The description does not add meaning beyond the schema, and schema coverage is 100%, achieving the baseline of 3.

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

Purpose5/5

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

The description '获取用户指定角色收藏信息' clearly states the action (get), the resource (user's character collection info), and the specificity (for a specified character). It distinguishes from the sibling tool 'get_user_character_collections' which likely returns all collections.

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?

The description implies this tool is for a single character via '指定角色', but no explicit guidance on when to use it versus alternatives like 'get_user_character_collections' is provided. Context from sibling names helps, but the description itself lacks explicit usage direction.

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

Deploy Server