Bangumi MCP

search_persons

Read-onlyIdempotent

Find anime, manga, and game related persons by keyword. Filter results by NSFW status and control output with limit and offset.

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": {
      "keyword": "<keyword>"
    },
    "name": "search_persons"
  }
}

Input Schema

Name	Required	Description
`keyword`	Yes	搜索关键词
`filter`	No	过滤条件，没有则不使用
`limit`	No	返回结果数量限制
`offset`	No	分页偏移量

Output Schema

Name	Required	Description	Default
`total`	No
`limit`	No
`offset`	No
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 18, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds no behavioral context (e.g., return format, pagination details). With annotations present, a 3 is appropriate as the description does not contradict but adds minimal value.

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?

Extremely concise (4 characters), but at the cost of helpful context. It is front-loaded but too minimal to fully inform the agent. Adequate for conciseness but not highly informative.

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?

Given the existence of output schema and annotations, the description still lacks guidance on when to use this tool over similar sibling tools (e.g., search_characters). It does not clarify the scope or filtering capabilities beyond the schema.

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?

All parameters are fully described in the schema (100% coverage). The description adds no parameter-specific information. Baseline 3 is appropriate.

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

Purpose3/5

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

The description '搜索人物' translates to 'Search persons', which states the verb and resource. However, it is very brief and does not distinguish from sibling tools like search_characters or search_subjects. It is not a tautology but lacks specificity.

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 (e.g., get_person_info for known IDs). The description does not mention context, prerequisites, or exclusions.

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

Deploy Server