AniList MCP Server

Overview Schema Source Related Servers Discussions Admin

Get an anime/manga's production staff

get_media_staff

Read-only

Retrieves an anime or manga's staff credits by AniList ID, listing each person's role such as director, writer, or character designer. Use search_media first to resolve a title to its ID.

Instructions

List an anime/manga's staff (director, writer, character designer, author, illustrator, etc.) with their role. Use search_media first to resolve a title to its AniList ID. No explicit ordering is requested — don't assume results are sorted by role or popularity (unlike get_staff's reverse-direction lookup, which IS popularity-sorted).

Input Schema

Name	Required	Description
`id`	Yes	AniList ID.
`page`	No	Page number for pagination. AniList's paginated connections (search results, a title's characters/staff/reviews, activity feeds, forum comments) reject a page whose page × perPage exceeds ~5000 entries with an upstream error, so paging that deep fails rather than returning more results.
`type`	Yes	Whether `id` refers to anime or manga.
`perPage`	No	Results per page (max 25, AniList's own ceiling — it silently clamps anything higher).

Output Schema

Name	Required	Description	Default
`staff`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.11.0Oct 25, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / perPage / description

Previous value: -"Results per page (max 50, AniList's own ceiling — it silently clamps anything higher)."New value: +"Results per page (max 25, AniList's own ceiling — it silently clamps anything higher)."

changedInput schema / properties / perPage / maximum
```
Previous value: -50New value: +25
```

Changed5 schema fields changedv0.9.0Sep 27, 2026

changedInput schema / properties / perPage / description

Previous value: -"Results per page (max 25)."New value: +"Results per page (max 50, AniList's own ceiling — it silently clamps anything higher)."

changedInput schema / properties / perPage / maximum
```
Previous value: -25New value: +50
```

changedOutput schema / properties / staff / properties / edges / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {
-        "node": {
-          "anyOf": [
-            {
-              "additionalProperties": {},
-              "properties": {
-                "id": {
-                  "exclusiveMinimum": 0,
-                  "maximum": 2147483647,
-                  "type": "integer"
-                },
-                "name": {
-                  "anyOf": [
-                    {
-                      "additionalProperties": false,
-                      "properties": {
-                        "full": {
-                          "anyOf": [
-                            {
-                              "type": "string"
-                            },
-                            {
-                              "type": "null"
-                            }
-                          ]
-                        }
-                      },
-                      "type": "object"
-                    },
-                    {
-                      "type": "null"
-                    }
-                  ]
-                }
-              },
-              "required": [
-                "id"
-              ],
-              "type": "object"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "role": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "node": {
+          "anyOf": [
+            {
+              "additionalProperties": {},
+              "properties": {
+                "id": {
+                  "exclusiveMinimum": 0,
+                  "maximum": 2147483647,
+                  "type": "integer"
+                },
+                "name": {
+                  "anyOf": [
+                    {
+                      "additionalProperties": false,
+                      "properties": {
+                        "full": {
+                          "type": [
+                            "string",
+                            "null"
+                          ]
+                        }
+                      },
+                      "type": "object"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                }
+              },
+              "required": [
+                "id"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "role": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / staff / properties / pageInfo / properties / hasNextPage / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / staff / properties / pageInfo / properties / hasNextPage / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

Changed6 schema fields changedv0.7.1Aug 1, 2026

addedInput schema / properties / id / exclusiveMinimum
```
Added value: +0
```
removedInput schema / properties / id / minimum
```
Removed value: --2147483648
```

changedInput schema / properties / page / description

Previous value: -"Page number for pagination."New value: +"Page number for pagination. AniList's paginated connections (search results, a title's characters/staff/reviews, activity feeds, forum comments) reject a page whose page × perPage exceeds ~5000 entries with an upstream error, so paging that deep fails rather than returning more results."

addedInput schema / properties / perPage / exclusiveMinimum
```
Added value: +0
```
removedInput schema / properties / perPage / minimum
```
Removed value: -1
```

changedOutput schema / properties / staff / properties / edges / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {
-        "node": {
-          "anyOf": [
-            {
-              "additionalProperties": {},
-              "properties": {
-                "id": {
-                  "maximum": 9007199254740991,
-                  "minimum": -9007199254740991,
-                  "type": "integer"
-                },
-                "name": {
-                  "anyOf": [
-                    {
-                      "additionalProperties": false,
-                      "properties": {
-                        "full": {
-                          "anyOf": [
-                            {
-                              "type": "string"
-                            },
-                            {
-                              "type": "null"
-                            }
-                          ]
-                        }
-                      },
-                      "type": "object"
-                    },
-                    {
-                      "type": "null"
-                    }
-                  ]
-                }
-              },
-              "required": [
-                "id"
-              ],
-              "type": "object"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "role": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "node": {
+          "anyOf": [
+            {
+              "additionalProperties": {},
+              "properties": {
+                "id": {
+                  "exclusiveMinimum": 0,
+                  "maximum": 2147483647,
+                  "type": "integer"
+                },
+                "name": {
+                  "anyOf": [
+                    {
+                      "additionalProperties": false,
+                      "properties": {
+                        "full": {
+                          "anyOf": [
+                            {
+                              "type": "string"
+                            },
+                            {
+                              "type": "null"
+                            }
+                          ]
+                        }
+                      },
+                      "type": "object"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                }
+              },
+              "required": [
+                "id"
+              ],
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "role": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedv0.3.0Jul 26, 2026

changedInput schema / properties / type / description

Previous value: -"Whether `id`/`ids` refers to anime or manga."New value: +"Whether `id` refers to anime or manga."

Addedv0.2.0Jul 21, 2026
Removedv0.2.0Jul 21, 2026
First observedv0.1.5Jul 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With readOnlyHint and openWorldHint already declaring the safety profile, the description contributes the non-obvious trait that results carry no guaranteed ordering — a genuine behavioral caveat an agent would otherwise mis-infer. It also flags the contrast with get_staff's sorting. It does not discuss result volume or pagination depth, but the schema already documents that.

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?

Three sentences, each carrying distinct information: what is returned, the ID-resolution prerequisite, and the ordering caveat. The final sentence is long but front-loads the caution ("No explicit ordering is requested") before the comparison, so it reads cleanly.

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?

For a 4-parameter read tool with a full schema and an output schema, the description covers the only things the structured fields cannot: how to obtain the ID and that ordering is unspecified. Nothing needed to call it correctly is missing.

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 coverage is 100%, including the pagination clamp and perPage ceiling, so the schema does the heavy lifting. The description reinforces that `type` selects anime vs manga and that `id` must come from search_media, but adds no format or edge-case detail beyond that.

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 ("List an anime/manga's staff ... with their role") and enumerates the role types returned. It explicitly distinguishes itself from get_staff by calling that tool a "reverse-direction lookup," so an agent can separate the two without opening schemas.

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 a concrete prerequisite workflow: use search_media first to resolve a title to an AniList ID. It also sets an expectation against a sibling (get_staff is popularity-sorted, this is not). It does not address other plausible siblings such as search_staff or get_character, so it falls just short of a full when/when-not guide.

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

Deploy Server