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 on AniList using its media ID. New entries default to CURRENT, existing ones keep unset fields unchanged. Requires login.

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. 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
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
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

The description goes far beyond annotations by disclosing upsert semantics, default-only-for-new-entries behavior, response echoing for verification, and the zero/replace behavior of `advancedScores` and `customLists`. It also reveals subtle API quirks (e.g., API defaults status to CURRENT while the UI defaults to PLANNING), which is exactly the kind of behavioral transparency needed for a mutation tool with openWorldHint=true.

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?

The description is long but every sentence carries critical information about defaults, upsert, response verification, and pitfalls. It is front-loaded with the required login and core purpose, then logically flows through prerequisites, behavior, and caveats. While dense, it earns its length for a tool with 14 parameters and subtle API semantics.

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 complexity (14 params, nested objects, output schema), the description is complete. It covers safety (requires login), workflow (search first), edge cases (upsert, defaults), and verification (response echoing). The output schema handles return values, so the description needn't explain them. It addresses all major scenarios an agent would face.

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%, the description adds substantial meaning beyond the schema: it explains the status default nuance per new vs existing entry, clarifies that `customLists` replaces rather than merges and requires pre-existing lists, and warns about `advancedScores` zeroing omitted categories and positional matching at read time. This enriches parameter usage significantly.

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 clear, specific verb+resource: 'Add an anime/manga to the authenticated user's own AniList list.' It distinguishes itself from siblings by explicitly covering upsert behavior (update-if-exists), which differentiates it from get_user_list and complements update_list_entry. It also states the prerequisite of using search_media first.

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?

Provides explicit usage guidance: 'Use search_media first to resolve the title to its AniList media ID' and 'Use get_user_list first to check for an existing entry if you need a guaranteed-fresh one.' It explains when defaults apply (new entries only) versus when they don't (existing entries keep previous values), giving clear context on when this tool is appropriate.

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