Skip to main content
Glama
Grinv

AniList MCP Server

Add an entry to your AniList list

add_list_entry

Add or update an anime/manga in your AniList list using its media ID, setting status, progress, score, notes, and more.

Instructions

[Requires login] Add an anime/manga to the authenticated user's own AniList list. Use search_media first to resolve the title to its AniList media ID. Only set the fields you care about — everything else is left at AniList's defaults ONLY if this media isn't already on the list. AniList upserts by media ID: if an entry for it already exists (e.g. previously dropped, with its own score/notes/progress), calling this updates that entry in place instead — every field you don't set here keeps its previous value, not a default. Use get_user_list first to check for an existing entry if you need a guaranteed-fresh one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoFree-text notes for this entry (per AniList's own schema, capped at 6000 characters).
scoreNoScore out of 10 (decimals allowed, e.g. 8.5), always on this scale regardless of the account's configured scoreFormat (set via update_user) — no conversion needed.
repeatNoNumber of times rewatched/reread (per AniList's own schema, capped at 1000).
statusNoList status. If omitted on a genuinely NEW entry, AniList defaults to CURRENT (with `startedAt` auto-set to today) — confirmed live; despite AniList's own site UI defaulting new entries to Planning, the API itself does not. If the media is already on the list, this default does NOT apply — omitting `status` on an update-in-place leaves the entry's existing status untouched.
mediaIdYesAniList anime/manga ID to add (from search_media).
privateNoHide this entry from your public list.
priorityNoList priority (higher = more important; per AniList's own schema, capped at 255).
progressNoEpisodes watched / chapters read.
startedAtNoDate you started.
completedAtNoDate you completed.
customListsNoNames of custom lists to file this entry under — 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), it doesn't leave them alone. Include every list name you want this entry to stay tagged with, not just the one you're adding. 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.
advancedScoresNoPer-category scores, 0-10 scale (e.g. {Story: 8, Characters: 9}) — errors if advanced scoring isn't enabled for this media's type, or if a key doesn't match the account's configured category list for it (anime and manga have SEPARATELY configured lists). Any of that list's categories you omit here is set to 0, not left unchanged — include every category if you don't want the others zeroed. Stored positionally, not by name: matched against the account's category order (update_user's `advancedScoring`) at READ time, not write time — if that order is later renamed/reordered, a score you write for 'Story' today can silently be read back as 'Characters' tomorrow, with no error.
progressVolumesNoVolumes read (manga only).
hiddenFromStatusListsNoHide 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
Behavior5/5

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

Beyond the annotations (which mark this as non-read-only), the description discloses critical behaviors: login requirement, upsert-by-mediaID semantics, that omitted fields keep previous values on existing entries, and that defaults only apply to genuinely new entries. These are meaningful behavioral details that the annotations alone do not capture.

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 dense but every sentence earns its place: prerequisites, default behavior, upsert semantics, and a cautionary recommendation to check get_user_list. It is front-loaded with the core action and immediately follows with the most important behavioral caveats.

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?

Given the tool's complexity—14 parameters, nested objects, and an output schema—the description is complete. It covers prerequisites, the upsert distinction, field-omission consequences, and key gotchas. Return values are already handled by the output schema, so the description focuses on the behavioral context that matters most.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100% and individual parameter descriptions are detailed, the description adds important nuances beyond the schema: the status default of CURRENT (not PLANNING), customLists replacing rather than merging, and advancedScores being stored positionally and zeroing omitted categories. This is substantial added semantic value.

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 opens with a specific verb and resource: 'Add an anime/manga to the authenticated user's own AniList list.' This clearly distinguishes the tool from siblings like update_list_entry and remove_list_entry, and the title reinforces the same purpose.

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?

The description gives clear sequencing guidance: use search_media first to resolve the ID, and get_user_list first to check for existing entries if a guaranteed-fresh one is needed. It explains when defaults apply vs. when in-place updates occur. However, it does not explicitly name update_list_entry as an alternative, though the upsert discussion makes the usage context clear.

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

Install Server

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