MAL MCP Server

by Grinv

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get top people

get_top_people

Read-only

Discover the top voice actors, staff, and authors. Paginate to view the overall ranking of people by favorites.

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

TableJSON Schema

Name	Required	Description	Default
`page`	No	1-based page number for pagination. No upper bound — this ranking runs to the end of MAL's own catalog.
`limit`	No	Max results per page (1-50).

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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.3/5.0

Behavior3/5

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

Annotations already cover read-only and open-world characteristics, so the description does not need to restate safety. The description adds useful context—that the ranking is global ('ranked overall') and limited to people categories—but does not disclose retrieval, pagination, or other behavior beyond what annotations and schema already make clear.

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 two concise sentences with no filler. The core purpose is front-loaded, and the routing to search_people is presented immediately after the main statement.

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

Completeness5/5

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

This is a simple read-only listing tool with optional pagination parameters and an output schema. The description plus schema fully covers what an agent needs to know: what the tool returns, when to use it, and when to use the sibling search_people instead.

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%, with both page and limit already documented. The tool description adds no parameter-level detail, but none is needed because the schema already provides meanings, defaults, ranges, and pagination behavior.

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 states a clear verb ('Get') and a specific resource ('the most popular/favorited people'), and further clarifies the domain as voice actors, staff, and authors. It also distinguishes itself from search_people, which is the sibling used for exact-name searches.

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?

The description explicitly says to use search_people when looking up a specific person by name, providing a clear when-not-to-use condition and alternative. The 'ranked overall' phrasing communicates that this tool is the right choice when the agent needs a broad popularity ranking rather than targeted lookup.

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

Deploy Server