MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get my MAL profile

get_my_user_info

Read-only

Retrieve the logged-in user's MyAnimeList profile and anime watch-status statistics. Requires a MyAnimeList login; returns anime-only data, not manga statistics.

Instructions

Get the logged-in user's MyAnimeList profile and anime watch-status statistics. Requires a MyAnimeList login. Anime-only — the official API has no manga statistics field at all, and there is no tool for a user's manga read stats.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`id`	Yes
`name`	Yes
`location`	No
`joined_at`	No
`anime_statistics`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.11.0Oct 25, 2026
- removedOutput schema / properties / location / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / location / type
```
Added value: +[
+  "string",
+  "null"
+]
```
Changed3 schema fields changedv0.9.0Jul 30, 2026
- addedOutput schema / properties / id / exclusiveMinimum
```
Added value: +0
```
- addedOutput schema / properties / id / maximum
```
Added value: +9007199254740991
```
- changedOutput schema / properties / id / type
```
Previous value: -"number"New value: +"integer"
```
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": {},
+  "properties": {
+    "anime_statistics": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "id": {
+      "type": "number"
+    },
+    "joined_at": {
+      "type": "string"
+    },
+    "location": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jun 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, which covers the safe-read profile. The description adds genuinely new behavioral context beyond them: authentication is required and the data domain is restricted to anime because the upstream API exposes no manga statistics field.

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?

Three short sentences, front-loaded with what is returned, then the auth prerequisite, then the scope caveat. Nothing is redundant and every sentence carries information an agent needs.

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?

An output schema exists, so return-value detail is unnecessary, and the tool takes no arguments. Given annotations already cover safety and openness, the description supplies exactly the missing pieces: auth requirement and the anime-only limitation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. 'Logged-in user' usefully confirms the identity is implicit (derived from session) rather than a caller-supplied argument.

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?

Specific verb+resource: returns the logged-in user's MAL profile plus anime watch-status statistics. It is clearly distinguished from siblings get_my_anime_list (list entries) and get_anime_statistics (site-wide stats), and the anime-only scope is stated up front.

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

Usage Guidelines4/5

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

Supplies the key prerequisite ('Requires a MyAnimeList login') and a negative rule that saves wasted calls: there is no manga-stats counterpart, so the agent should not go hunting for one. It stops short of explicitly naming get_my_manga_list or login_mal as the fallback/routing options.

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

Deploy Server