MAL MCP Server

Get person details

get_person

Read-only

Retrieve a person's full MyAnimeList profile by mal_id: biography, anime/manga staff credits, and voiced roles. Optionally filter adult content or fetch the complete staff credit list.

Instructions

Get full details for one person by mal_id: bio, their anime/manga staff-credit lists, and their voiced roles. Staff credits are capped at the first 200 (only an extreme outlier hits that — a prolific sound director can have 500+; a well-known director sits under 100); when the cap bites, the response says so via credits_truncated plus total_anime_credits/total_manga_credits, and full_credits: true returns every entry. voice_roles is separately capped at the first 50, in whatever order the upstream API returns them (not necessarily their most notable roles). Obtain the mal_id from search_people, or from get_character's voice_actors (which include each actor's mal_id — get_anime_characters' voice_actors are names only, with no id). sfw/sfw_strict filter NSFW/adult-adjacent titles out of the person's own anime/manga credit lists (verified live) rather than affecting the person themselves.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	MyAnimeList numeric ID.
`sfw`	No	If true, exclude adult/explicit-rated entries (R+ Mild Nudity and up). Defaults to false (no filtering). Note: this alone still allows mainstream, safely-rated shows tagged with the Ecchi genre (fanservice) through — use `sfw_strict` to also exclude those.
`sfw_strict`	No	If true, exclude adult/explicit-rated entries AND anything tagged with the Ecchi genre, even otherwise-mainstream/safely-rated shows. Stricter than `sfw` alone. Defaults to false.
`full_credits`	No	If true, return every staff credit instead of the first 200. Only needed for the handful of people whose response reports `credits_truncated`. Defaults to false.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No
`name`	No
`about`	No
`anime`	No
`manga`	No
`mal_id`	Yes
`birthday`	No
`favorites`	No
`image_url`	No
`given_name`	No
`family_name`	No
`voice_roles`	No
`alternate_names`	No
`credits_truncated`	No
`total_anime_credits`	No
`total_manga_credits`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedv0.10.0Aug 24, 2026

addedInput schema / properties / full_credits

Added value: +{
+  "description": "If true, return every staff credit instead of the first 200. Only needed for the handful of people whose response reports `credits_truncated`. Defaults to false.",
+  "type": "boolean"
+}

addedOutput schema / properties / credits_truncated

Added value: +{
+  "const": true,
+  "type": "boolean"
+}

addedOutput schema / properties / total_anime_credits

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / total_manga_credits

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

Changed17 schema fields changedv0.9.0Jul 30, 2026
- addedInput schema / properties / sfw
```
Added value: +{
+  "description": "If true, exclude adult/explicit-rated entries (R+ Mild Nudity and up). Defaults to false (no filtering). Note: this alone still allows mainstream, safely-rated shows tagged with the Ecchi genre (fanservice) through — use `sfw_strict` to also exclude those.",
+  "type": "boolean"
+}
```
- addedInput schema / properties / sfw_strict
```
Added value: +{
+  "description": "If true, exclude adult/explicit-rated entries AND anything tagged with the Ecchi genre, even otherwise-mainstream/safely-rated shows. Stricter than `sfw` alone. Defaults to false.",
+  "type": "boolean"
+}
```
- addedOutput schema / properties / anime / items / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / anime / items / properties / mal_id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / anime / items / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / anime / items / required
```
Added value: +[
+  "mal_id"
+]
```
- addedOutput schema / properties / favorites / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / favorites / minimum
```
Added value: +0
```
- changedOutput schema / properties / favorites / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / mal_id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / manga / items / properties / mal_id / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / manga / items / properties / mal_id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / manga / items / properties / mal_id / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / manga / items / required
```
Added value: +[
+  "mal_id"
+]
```
- addedOutput schema / required
```
Added value: +[
+  "mal_id"
+]
```
Changed1 schema field changedv0.8.0Jul 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed2 schema fields changedv0.7.1Jul 22, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "about": {
+      "type": "string"
+    },
+    "alternate_names": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "anime": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "mal_id": {
+            "type": "number"
+          },
+          "position": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "birthday": {
+      "type": "string"
+    },
+    "family_name": {
+      "type": "string"
+    },
+    "favorites": {
+      "type": "number"
+    },
+    "given_name": {
+      "type": "string"
+    },
+    "image_url": {
+      "type": "string"
+    },
+    "mal_id": {
+      "type": "number"
+    },
+    "manga": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "mal_id": {
+            "type": "number"
+          },
+          "position": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "name": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    },
+    "voice_roles": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "anime": {
+            "type": "string"
+          },
+          "character": {
+            "type": "string"
+          },
+          "role": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Addedv0.2.0Jun 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description reveals important non-obvious behaviors beyond the readOnlyHint: staff credits are capped at 200 with truncation flags, voice roles capped at 50 in arbitrary order, sfw filters apply only to the credit lists, and full_credits returns everything. This is exactly the kind of edge-case behavior an agent needs to know.

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

Conciseness4/5

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

The description packs a lot of useful nuance into a compact paragraph, but it is dense and somewhat sprawling rather than well-structured. The first sentence is a clear purpose statement, and the rest earns its place, though it could be tightened by using bullet points or shorter sentences.

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?

Given the rich output schema and high schema coverage, the description adequately covers the essential context: how to source the id, what the limits are, what filtering does, and how to get full results. There's no glaring gap for an agent to call this tool correctly.

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 schema already covers all parameters with detailed descriptions, including edge-case notes for sfw vs sfw_strict, so the description adds little per-parameter meaning. It does add value by explaining the interaction of full_credits with the credits_truncated flag, but most parameter meaning is already in the schema.

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 identifies the resource (person by mal_id) and enumerates the distinct data returned: bio, staff credits, and voiced roles. It explicitly names the sibling search_people and get_character, making it easy for an agent to distinguish this tool from related lookups.

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?

Exactly when to use is stated: to fetch a single person's full details by mal_id, and the description explains how to obtain the mal_id from search_people or get_character. It also distinguishes get_character's voice_actors (with id) from get_anime_characters' (no id), giving clear alternatives and routing.

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

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Grinv/mal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server