AniList MCP Server

Overview Schema Source Related Servers Discussions Admin

Update an entry on your AniList list

update_list_entry

Idempotent

Update an existing entry on the authenticated user's AniList list by list-entry ID, changing only the fields you specify, such as status, score, progress, dates, or notes.

Instructions

[Requires login] Update an existing entry on the authenticated user's own AniList list by its list-entry ID (NOT the media ID — get it from get_user_list, or from add_list_entry's response). Only set the fields you want to change. Updating MANY entries to the SAME values? Use update_list_entries instead — one request rather than one per entry. The response echoes what AniList actually stored, so check it rather than assuming the write landed verbatim. It includes customLists/advancedScores only when you set them — those are the fields AniList zeroes/replaces rather than merges; otherwise the echo is trimmed.

Input Schema

Name	Required	Description
`notes`	No	New free-text notes (per AniList's own schema, capped at 6000 characters).
`score`	No	New score out of 10 (decimals allowed), always on this scale regardless of the account's configured scoreFormat (set via update_user) — no conversion needed.
`repeat`	No	New rewatch/reread count (per AniList's own schema, capped at 1000).
`status`	No	New list status.
`private`	No	Hide/unhide this entry from your public list.
`priority`	No	New list priority (higher = more important; per AniList's own schema, capped at 255).
`progress`	No	New episodes watched / chapters read.
`startedAt`	No	New start date.
`completedAt`	No	New completion date.
`customLists`	No	New set of custom lists for this entry — REPLACES this entry's full set of enabled lists, not merged: naming only a subset silently turns OFF every other list this entry was previously filed under (confirmed live for add_list_entry's identical field; this tool writes the same underlying value), it doesn't leave them alone. Include every list name you want this entry to stay tagged with, not just the one you're changing. Also, the list must already exist on the account (update_user's `animeListOptions`/`mangaListOptions` `customLists`) — naming one that doesn't exist yet is silently a no-op, not an error.
`listEntryId`	Yes	The list ENTRY id to update (not the media id).
`advancedScores`	No	New per-category scores, keyed and error-checked the same way as add_list_entry (errors if advanced scoring is disabled, or a key doesn't match a configured category). Unlike this tool's other fields, this one is NOT a true partial update: any configured category you omit is set to 0, not left at its previous value — pass every category if you're only changing one. Also stored positionally, not by name — same read-time reinterpretation risk as add_list_entry's `advancedScores` if the account's category order (update_user's `advancedScoring`) is later renamed/reordered.
`progressVolumes`	No	New volumes read (manga only).
`hiddenFromStatusLists`	No	Hide/unhide this entry from the public status-grouped list views (e.g. 'Watching') while still counting it in statistics — distinct from `private`, which hides the entry entirely.

Output Schema

Name	Required	Description	Default
`entry`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.11.0Oct 25, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / completedAt / properties / year / description
```
Added value: +"Required — omit the whole date to leave it unchanged."
```
addedInput schema / properties / completedAt / required
```
Added value: +[
+  "year"
+]
```
addedInput schema / properties / startedAt / properties / year / description
```
Added value: +"Required — omit the whole date to leave it unchanged."
```
addedInput schema / properties / startedAt / required
```
Added value: +[
+  "year"
+]
```

changedOutput schema / properties / entry / properties / advancedScores / description

Previous value: -"Per-category advanced scores as AniList actually stores them — an untyped value (the write side takes a plain {category: score} map via add_list_entry/update_list_entry's `advancedScores`, but the echoed read-back shape isn't guaranteed to match it)."New value: +"Per-category advanced scores as AniList actually stores them, as a {category: score} map on the same 0-10 scale as `score` (so a value read here can be passed straight back to add_list_entry/update_list_entry's `advancedScores`). Every configured category is present — AniList stores 0 for any not set."

Changed10 schema fields changedv0.9.0Sep 27, 2026

changedOutput schema / properties / entry / properties / customLists / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "properties": {
-        "enabled": {
-          "anyOf": [
-            {
-              "type": "boolean"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        },
-        "name": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "enabled": {
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / entry / properties / hiddenFromStatusLists / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / entry / properties / hiddenFromStatusLists / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

removedOutput schema / properties / entry / properties / notes / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / entry / properties / notes / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / entry / properties / private / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / entry / properties / private / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

addedOutput schema / properties / entry / properties / score / description

Added value: +"This user's own score for the entry, on a 0-10 scale (decimals allowed). It stays 0-10 on every account whatever the configured scoreFormat is, and matches the scale add_list_entry/update_list_entry take on write. This is NOT the 0-100 scale `averageScore`/`meanScore`/search_media's `averageScore_greater` filter use."

removedOutput schema / properties / entry / properties / status / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / entry / properties / status / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed12 schema fields changedv0.8.0Aug 17, 2026

addedOutput schema / $defs

Added value: +{
+  "__schema0": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "type": "null"
+      },
+      {
+        "items": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "type": "array"
+      },
+      {
+        "additionalProperties": {
+          "$ref": "#/$defs/__schema0"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      }
+    ]
+  }
+}

addedOutput schema / properties / entry / properties / advancedScores

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/__schema0"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Per-category advanced scores as AniList actually stores them — an untyped value (the write side takes a plain {category: score} map via add_list_entry/update_list_entry's `advancedScores`, but the echoed read-back shape isn't guaranteed to match it)."
+}

addedOutput schema / properties / entry / properties / completedAt

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "day": {
+          "anyOf": [
+            {
+              "exclusiveMinimum": 0,
+              "maximum": 9007199254740991,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "month": {
+          "anyOf": [
+            {
+              "exclusiveMinimum": 0,
+              "maximum": 9007199254740991,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "year": {
+          "anyOf": [
+            {
+              "exclusiveMinimum": 0,
+              "maximum": 9007199254740991,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / entry / properties / createdAt

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / entry / properties / customLists

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "enabled": {
+            "anyOf": [
+              {
+                "type": "boolean"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "name": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Every custom list configured on the account, with `enabled` showing whether THIS entry is filed under it. Naming a list here (via add_list_entry/update_list_entry) that isn't already in the account's `animeListOptions`/`mangaListOptions` `customLists` is silently a no-op on write — the list must exist first."
+}

addedOutput schema / properties / entry / properties / notes

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / entry / properties / priority

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / entry / properties / private

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / entry / properties / progressVolumes

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / entry / properties / repeat

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / entry / properties / startedAt

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {},
+      "properties": {
+        "day": {
+          "anyOf": [
+            {
+              "exclusiveMinimum": 0,
+              "maximum": 9007199254740991,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "month": {
+          "anyOf": [
+            {
+              "exclusiveMinimum": 0,
+              "maximum": 9007199254740991,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "year": {
+          "anyOf": [
+            {
+              "exclusiveMinimum": 0,
+              "maximum": 9007199254740991,
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / entry / properties / updatedAt

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed15 schema fields changedv0.7.1Aug 1, 2026

changedInput schema / properties / advancedScores / description

Previous value: -"New per-category scores, keyed and error-checked the same way as add_list_entry (errors if advanced scoring is disabled, or a key doesn't match a configured category). Unlike this tool's other fields, this one is NOT a true partial update: any configured category you omit is set to 0, not left at its previous value — pass every category if you're only changing one."New value: +"New per-category scores, keyed and error-checked the same way as add_list_entry (errors if advanced scoring is disabled, or a key doesn't match a configured category). Unlike this tool's other fields, this one is NOT a true partial update: any configured category you omit is set to 0, not left at its previous value — pass every category if you're only changing one. Also stored positionally, not by name — same read-time reinterpretation risk as add_list_entry's `advancedScores` if the account's category order (update_user's `advancedScoring`) is later renamed/reordered."

addedInput schema / properties / completedAt / properties / year / exclusiveMinimum
```
Added value: +0
```
removedInput schema / properties / completedAt / properties / year / minimum
```
Removed value: --9007199254740991
```

changedInput schema / properties / customLists / description

Previous value: -"New set of custom lists for this entry. The list must already exist on the account (update_user's `animeListOptions`/`mangaListOptions` `customLists`) — naming one that doesn't exist yet is silently a no-op, not an error."New value: +"New set of custom lists for this entry — REPLACES this entry's full set of enabled lists, not merged: naming only a subset silently turns OFF every other list this entry was previously filed under (confirmed live for add_list_entry's identical field; this tool writes the same underlying value), it doesn't leave them alone. Include every list name you want this entry to stay tagged with, not just the one you're changing. Also, the list must already exist on the account (update_user's `animeListOptions`/`mangaListOptions` `customLists`) — naming one that doesn't exist yet is silently a no-op, not an error."

changedInput schema / properties / hiddenFromStatusLists / description

Previous value: -"Hide/unhide this entry from the public status-grouped list views — distinct from `private`, which hides the entry entirely."New value: +"Hide/unhide this entry from the public status-grouped list views (e.g. 'Watching') while still counting it in statistics — distinct from `private`, which hides the entry entirely."

addedInput schema / properties / listEntryId / exclusiveMinimum
```
Added value: +0
```
removedInput schema / properties / listEntryId / minimum
```
Removed value: --2147483648
```
addedInput schema / properties / startedAt / properties / year / exclusiveMinimum
```
Added value: +0
```
removedInput schema / properties / startedAt / properties / year / minimum
```
Removed value: --9007199254740991
```
addedOutput schema / properties / entry / properties / id / exclusiveMinimum
```
Added value: +0
```
changedOutput schema / properties / entry / properties / id / maximum
```
Previous value: -9007199254740991New value: +2147483647
```
removedOutput schema / properties / entry / properties / id / minimum
```
Removed value: --9007199254740991
```

changedOutput schema / properties / entry / properties / mediaId / anyOf

Previous value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 2147483647,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / entry / properties / progress / anyOf

Previous value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / entry / properties / score / anyOf

Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]

Changed6 schema fields changedv0.5.0Jul 29, 2026

changedInput schema / properties / notes / description

Previous value: -"New free-text notes."New value: +"New free-text notes (per AniList's own schema, capped at 6000 characters)."

addedInput schema / properties / notes / maxLength
```
Added value: +6000
```

changedInput schema / properties / priority / description

Previous value: -"New list priority."New value: +"New list priority (higher = more important; per AniList's own schema, capped at 255)."

changedInput schema / properties / priority / maximum
```
Previous value: -9007199254740991New value: +255
```

changedInput schema / properties / repeat / description

Previous value: -"New rewatch/reread count."New value: +"New rewatch/reread count (per AniList's own schema, capped at 1000)."

changedInput schema / properties / repeat / maximum

Previous value: -9007199254740991New value: +1000

Changed3 schema fields changedv0.3.0Jul 26, 2026

addedInput schema / properties / advancedScores / additionalProperties / maximum
```
Added value: +10
```
addedInput schema / properties / advancedScores / additionalProperties / minimum
```
Added value: +0
```

changedInput schema / properties / advancedScores / description

Previous value: -"New per-category scores, keyed the same way as add_list_entry. Unlike this tool's other fields, this one is NOT a true partial update: any configured category you omit is set to 0, not left at its previous value — pass every category if you're only changing one."New value: +"New per-category scores, keyed and error-checked the same way as add_list_entry (errors if advanced scoring is disabled, or a key doesn't match a configured category). Unlike this tool's other fields, this one is NOT a true partial update: any configured category you omit is set to 0, not left at its previous value — pass every category if you're only changing one."

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

TDQS

A4.7/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description still adds real value: a login requirement, the fact that the response echoes what AniList actually stored rather than the request, and that customLists/advancedScores are replaced/zeroed rather than merged. No contradiction with the non-destructive, idempotent hints.

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?

Front-loaded with the login requirement and ID sourcing, then batch alternative, then response caveats. Every sentence carries information, though the final clause about the trimmed echo is densely packed and takes a second read.

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?

Covers auth, ID provenance, partial-update behavior, bulk alternative, and known data-loss traps. An output schema exists so return values needn't be spelled out, but the description still explains the echo's shape; little is missing for a 14-parameter mutation tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds the governing partial-update contract ('only set the fields you want to change') and flags the two exception fields whose semantics differ from the rest, which the per-parameter schema text alone makes easy to miss.

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+resource+scope: updates an existing entry on the authenticated user's own list. It explicitly disambiguates the identifier ('list-entry ID, NOT the media ID') and names the bulk sibling update_list_entries, so an agent can route without opening the schema.

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?

Gives explicit when-to-use ('only set the fields you want to change'), an explicit alternative with the selecting condition ('updating MANY entries to the SAME values? use update_list_entries — one request rather than one per entry'), and tells where to obtain the entry ID (get_user_list, add_list_entry response).

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

Deploy Server