Skip to main content
Glama
Grinv

AniList MCP Server

Update an entry on your AniList list

update_list_entry
Idempotent

Update a specific entry on your AniList, identified by its list-entry ID, to change status, score, progress, notes, dates, and more.

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. The response echoes every field this tool can set, as AniList actually stored it — check it instead of assuming the write landed verbatim, especially for advancedScores and customLists, which AniList zeroes/replaces rather than merges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoNew free-text notes (per AniList's own schema, capped at 6000 characters).
scoreNoNew score out of 10 (decimals allowed), always on this scale regardless of the account's configured scoreFormat (set via update_user) — no conversion needed.
repeatNoNew rewatch/reread count (per AniList's own schema, capped at 1000).
statusNoNew list status.
privateNoHide/unhide this entry from your public list.
priorityNoNew list priority (higher = more important; per AniList's own schema, capped at 255).
progressNoNew episodes watched / chapters read.
startedAtNoNew start date.
completedAtNoNew completion date.
customListsNoNew 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.
listEntryIdYesThe list ENTRY id to update (not the media id).
advancedScoresNoNew 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.
progressVolumesNoNew volumes read (manga only).
hiddenFromStatusListsNoHide/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

TableJSON Schema
NameRequiredDescriptionDefault
entryYes
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate mutation, but the description adds critical behavioral details: response echoes stored values, advancedScores and customLists are zeroed/replaced rather than merged, and login is required. This goes beyond the annotation flags to inform the agent of side effects and verification steps.

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?

The description is compact, front-loaded with the core action, and every sentence delivers essential information (auth, ID distinction, partial update guidance, response verification). No filler.

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 complex tool with 14 params and nested objects, the description covers the key operational context: how to identify the entry, the partial-update model, special zeroing behavior, and the need to verify responses. Output schema exists, so return details are not needed.

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 baseline is 3. The tool description adds crucial parameter behavior for advancedScores and customLists (zeroed/replaced, not merged), which is not obvious from the schema alone. This lifts the score above baseline.

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 clearly states it updates an existing entry on the authenticated user's own AniList list by list-entry ID, explicitly distinguishing from media ID. It effectively contrasts with sibling tools like add_list_entry by specifying the exact action and resource.

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?

Provides clear usage context: requires login, update existing entry, only set fields to change, and points to get_user_list/add_list_entry response to obtain the list-entry ID. It lacks explicit 'do not use for' exclusions, but the context and sibling names make usage clear.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Grinv/anilist-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server