MAL MCP Server

Overview Schema Source Related Servers Discussions Admin

Get producers/studios

get_producers

Read-only

List and search anime producers and studios by name, letter, or sort order, returning MyAnimeList IDs and counts for discovery and pagination.

Instructions

List or search anime producers and studios with their MAL IDs and counts. Use q to search by name, then get_producer for one studio's full profile (about text, external links).

Input Schema

Name	Required	Description
`q`	No	Filter by name.
`page`	No	1-based page number for pagination (1-20000).
`sort`	No	Sort direction. Only takes effect together with `order_by`; ignored on its own.
`limit`	No	Max results per page (1-100).
`letter`	No	Restrict results to entries whose title starts with this single letter.
`order_by`	No	Field to order by.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 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 (1-1000)."New value: +"1-based page number for pagination (1-20000)."

changedInput schema / properties / page / maximum
```
Previous value: -1000New value: +20000
```
addedInput schema / properties / q / maxLength
```
Added value: +300
```
addedInput schema / properties / q / minLength
```
Added value: +1
```

changedInput schema / properties / sort / description

Previous value: -"Sort direction."New value: +"Sort direction. Only takes effect together with `order_by`; ignored on its own."

changedOutput schema / properties / results / items / properties / established / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"

Changed27 schema fields changedv0.9.0Jul 30, 2026
- addedInput schema / properties / letter
```
Added value: +{
+  "description": "Restrict results to entries whose title starts with this single letter.",
+  "maxLength": 1,
+  "minLength": 1,
+  "type": "string"
+}
```
- 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 (1-1000)."
```
- changedInput schema / properties / page / maximum
```
Previous value: -9007199254740991New value: +1000
```
- changedInput schema / properties / sort / enum
```
Previous value: -[
-  "desc",
-  "asc"
-]New value: +[
+  "asc",
+  "desc"
+]
```
- 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 / count / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / results / items / properties / count / minimum
```
Added value: +0
```
- changedOutput schema / properties / results / items / properties / count / type
```
Previous value: -"number"New value: +"integer"
```
- addedOutput schema / properties / results / items / properties / established / format
```
Added value: +"date-time"
```
- addedOutput schema / properties / results / items / properties / established / pattern
```
Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
```
- 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 / 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": {
+    "page": {
+      "additionalProperties": false,
+      "properties": {
+        "current_page": {
+          "type": "number"
+        },
+        "has_next_page": {
+          "type": "boolean"
+        },
+        "last_visible_page": {
+          "type": "number"
+        },
+        "total": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "count": {
+            "type": "number"
+          },
+          "established": {
+            "type": "string"
+          },
+          "favorites": {
+            "type": "number"
+          },
+          "image_url": {
+            "type": "string"
+          },
+          "mal_id": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results",
+    "page"
+  ],
+  "type": "object"
+}

Addedv0.2.0Jun 29, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare this is a read-only, open-world operation, so the safety profile is covered. The description adds useful context that results are summary records with IDs and counts and that full profile data requires a follow-up call, but it does not discuss pagination limits, sort interactions, or open-world coverage caveats.

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 tightly packed sentences front-load the purpose and end with the alternative detail tool. Every sentence carries routing or scope information with no filler.

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?

With a full schema, an output schema, and read-only/open-world annotations, the description supplies the remaining decision-critical context: what the list returns at a summary level and when to switch to get_producer. Minor omission of pagination behavior is covered by 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?

Schema description coverage is 100%, so every parameter is already documented, including the `sort`/`order_by` dependency and pagination limits. The description only calls out `q`, which repeats schema information rather than adding new syntax or filtering semantics.

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 specific verb and resource ('List or search anime producers and studios') and adds the key payload detail ('MAL IDs and counts'). It explicitly contrasts this summary-list tool with get_producer for full profiles, so the agent can distinguish it from its closest sibling without opening either schema.

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?

Gives clear routing: use `q` to search by name and use get_producer when a single studio's full profile is needed. It provides a positive alternative for the detail case but does not explicitly state exclusions or when not to use this tool.

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

Deploy Server