Skip to main content
Glama
Grinv

AniList MCP Server

Add an entry to your AniList list

add_list_entry

Add an anime or manga to your AniList list using its media ID. Optionally specify status, score, progress, and other details.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoFree-text notes for this entry.
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.
statusNoList status. If omitted, 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.
mediaIdYesAniList anime/manga ID to add (from search_media).
privateNoHide this entry from your public list.
priorityNoList priority (higher = more important).
progressNoEpisodes watched / chapters read.
startedAtNoDate you started.
completedAtNoDate you completed.
customListsNoNames of custom lists to file this entry under. 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}) — only meaningful if the account has advanced scoring enabled for this media's type. Anime and manga have SEPARATELY configured category lists, so keys must match whichever list applies to this entry. 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.
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
Behavior4/5

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

The description adds authentication requirements and default behavior beyond annotations. Annotations already indicate non-read-only and non-destructive, which are consistent. No contradictions.

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?

Three concise sentences covering login requirement, prerequisite, and best practice. No verbose or irrelevant content.

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?

Given 14 parameters (1 required) and an output schema, the description is sufficient to understand the tool's purpose and prerequisites. It does not cover error handling or output details, but output schema exists.

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% with detailed descriptions per parameter. The description adds global context about defaults and partial updates, which complements schema details.

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 the action ('Add an anime/manga') and the resource ('to the authenticated user's own AniList list'). It distinguishes from sibling tools like search_media (prerequisite) and remove_list_entry (by verb).

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?

It provides a prerequisite ('use search_media first') and a usage tip ('only set the fields you care about'). However, it does not explicitly differentiate when to use this vs update_list_entry or when not to use it.

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