AniList MCP Server

Overview Schema Source Related Servers Discussions Admin

Get an anime/manga's production staff

get_media_staff

Read-only

Retrieve the staff list for an anime or manga by its AniList ID, showing each member's role such as director, writer, or illustrator.

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

TableJSON 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).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`staff`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

Behavior4/5

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

With readOnlyHint and openWorldHint annotations covering the read-only nature, the description adds a non-obvious behavior: 'No explicit ordering is requested — don't assume results are sorted by role or popularity (unlike get_staff ... which IS popularity-sorted).' This adds useful caveat beyond the annotations.

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 sentences with no filler: the first states the action and scope, the second provides workflow and ordering caveat. Information is front-loaded and economical.

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?

The description covers the core purpose, prerequisite workflow (search_media), and a key behavioral caveat (unsorted results). The output schema exists, and annotations cover safety and open-world nature, so no critical context 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% with clear descriptions for all four parameters (id, type, page, perPage). The description only ties `id` to the search_media workflow but adds no parameter-specific syntax or constraints beyond the schema, so the baseline of 3 applies.

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 'List an anime/manga's staff (director, writer, character designer, author, illustrator, etc.) with their role.' This is a specific verb+resource+scope that clearly distinguishes from sibling tools, especially by noting 'unlike get_staff's reverse-direction lookup'.

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?

Explicit workflow guidance is provided: 'Use search_media first to resolve a title to its AniList ID.' It also contrasts with get_staff, telling the agent when not to use this tool, making the usage context unambiguous.

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

Deploy Server