MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get top people

get_top_people

Read-only

Fetch ranked popularity lists of voice actors, staff, and authors on MyAnimeList, with page and limit controls, to discover popular people in anime and manga.

Instructions

Get the most popular/favorited people (voice actors, staff, authors), ranked overall. Use search_people instead to look up a specific person by name.

Input Schema

Name	Required	Description	Default
`page`	No	1-based page number for pagination (1-20000).
`limit`	No	Max results per page (1-100).

Output Schema

Name	Required	Description	Default
`page`	Yes
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.11.0Oct 25, 2026

changedInput schema / properties / limit / description

Previous value: -"Max results per page (1-50)."New value: +"Max results per page (1-100)."

changedInput schema / properties / limit / maximum
```
Previous value: -50New value: +100
```

changedInput schema / properties / page / description

Previous value: -"1-based page number for pagination. No upper bound — this ranking runs to the end of MAL's own catalog."New value: +"1-based page number for pagination (1-20000)."

changedInput schema / properties / page / maximum

Previous value: -9007199254740991New value: +20000

Changed3 schema fields changedv0.10.0Aug 24, 2026
- addedOutput schema / properties / results / items / properties / credits_truncated
```
Added value: +{
+  "const": true,
+  "type": "boolean"
+}
```
- addedOutput schema / properties / results / items / properties / total_anime_credits
```
Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
```
- addedOutput schema / properties / results / items / properties / total_manga_credits
```
Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
```
Changed27 schema fields changedv0.9.0Jul 30, 2026
- changedInput schema / properties / limit / description
```
Previous value: -"Max results per page (1-25)."New value: +"Max results per page (1-50)."
```
- changedInput schema / properties / limit / maximum
```
Previous value: -25New value: +50
```
- changedInput schema / properties / page / description
```
Previous value: -"1-based page number for pagination."New value: +"1-based page number for pagination. No upper bound — this ranking runs to the end of MAL's own catalog."
```
- addedOutput schema / properties / page / properties / current_page / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / page / properties / current_page / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / page / properties / current_page / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / page / properties / last_visible_page / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / page / properties / last_visible_page / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / page / properties / last_visible_page / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / page / properties / total / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / page / properties / total / minimum
```
Added value: +0
```
- changedOutput schema / properties / page / properties / total / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / results / items / properties / anime / items / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / results / items / properties / anime / items / properties / mal_id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / results / items / properties / anime / items / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / results / items / properties / anime / items / required
```
Added value: +[
+  "mal_id"
+]
```
- addedOutput schema / properties / results / items / properties / favorites / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / results / items / properties / favorites / minimum
```
Added value: +0
```
- changedOutput schema / properties / results / items / properties / favorites / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / results / items / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / results / items / properties / mal_id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / results / items / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / results / items / properties / manga / items / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / results / items / properties / manga / items / properties / mal_id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / results / items / properties / manga / items / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / results / items / properties / manga / items / required
```
Added value: +[
+  "mal_id"
+]
```
- addedOutput schema / properties / results / items / required
```
Added value: +[
+  "mal_id"
+]
```
Addedv0.8.0Jul 29, 2026
Removedv0.7.1Jul 22, 2026
Addedv0.2.0Jun 29, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and side-effect profile are covered. The description adds ranking/ordering semantics ('ranked overall', favorited-based) but says nothing about rate limits, pagination behavior beyond the schema, or result shape. With annotations carrying the safety burden, a 3 is appropriate.

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?

Two sentences, zero waste, with the purpose stated first and the sibling disambiguation second. Nothing extraneous and nothing buried.

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?

An output schema exists so return values needn't be explained, and both params are fully specified in the schema. The only minor gap is a lack of guidance on default result count when no params are supplied, but for a simple ranked-list tool the definition is otherwise complete.

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%; both parameters (page 1-20000, limit 1-100) are fully documented with ranges in the schema. The description adds nothing about pagination or default page size, so the baseline 3 applies when the schema does all the work.

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?

States a specific verb and resource ('Get the most popular/favorited people') with concrete examples (voice actors, staff, authors) and defines what 'top' means (popularity/favorites, ranked overall). It explicitly distinguishes itself from search_people, so an agent can separate it from siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly names the alternative and the condition that selects it: 'Use search_people instead to look up a specific person by name.' This is the exact routing decision an agent needs when choosing between browsing top lists and looking up a known person.

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

Deploy Server