Skip to main content
Glama
Grinv

AniList MCP Server

Update your AniList account settings

update_user
Idempotent

Update your AniList account settings: profile text, preferred language, adult content visibility, score format, notification preferences, and anime/manga list options.

Instructions

[Requires login] Update settings on the authenticated user's own AniList account (about text, preferred title language, adult-content visibility, score format, notification/messaging preferences, anime/manga list options). Only set the fields you want to change — most fields are a true partial update (see notificationOptions/disabledListActivity below for the two confirmed exceptions). Note: this mutation isn't atomic — confirmed live that rejecting one invalid field (e.g. an incomplete disabledListActivity) can still leave OTHER fields from that same call applied. If a call errors, re-check with get_authorized_user rather than assuming nothing changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aboutNoNew profile 'about' text.
rowOrderNoInternal list-table row ordering key — reads back from `mediaListOptions.rowOrder` in the profile tools/this tool's own response.
timezoneNoDisplay timezone (e.g. "+09:00").
scoreFormatNoPreferred list score format (affects how scores DISPLAY on anilist.co only — add_list_entry/update_list_entry's `score` parameter always stays on a 0-10 scale regardless of this setting, so no conversion is needed on your end).
donatorBadgeNoCustom donator badge text (only takes effect on a donator account).
profileColorNoProfile accent color (name or hex).
titleLanguageNoPreferred title display language.
animeListOptionsNoNew anime-list display/scoring options — only the fields you set are changed (confirmed live: this is a partial merge, unlike add_list_entry's advancedScores).
mangaListOptionsNoNew manga-list display/scoring options — same partial-merge behavior as `animeListOptions` above.
activityMergeTimeNoMinutes within which consecutive list activity posts get merged into one.
staffNameLanguageNoPreferred staff/character name display language.
airingNotificationsNoWhether to notify about new episode airings for anime on your list.
displayAdultContentNoWhether to show adult content in search/browse.
notificationOptionsNoALL 20 notification types, every time — confirmed live this is a full replace, not a partial merge: AniList silently drops every type you don't list (not just resets it to default, removes it) with no error. Fetch the account's current list first (get_authorized_user's `options.notificationOptions`) and resend it in full with just your changes applied.
disabledListActivityNoALL 6 list statuses, every time — confirmed live: AniList rejects this with a 400 error if any status is missing ("Incorrect number of disabled list activity options"), it's not a partial per-status update. Fetch the current list first (get_authorized_user's `options.disabledListActivity`) and resend it in full with just your changes applied.
restrictMessagesToFollowingNoOnly allow message activity from users you follow.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
userYes
Behavior5/5

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

The description discloses critical behavioral traits beyond annotations: non-atomic mutation, partial update for most fields but full replace for notificationOptions and disabledListActivity, and that rejecting one field can leave others applied. This adds significant value beyond the readOnlyHint=false, idempotentHint=true, destructiveHint=false annotations.

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 lengthy but every sentence serves a purpose. It is well-structured with clear sections and front-loaded with the login requirement and scope. Minor redundancy could be trimmed, but overall efficient for the complexity.

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 (16 parameters, nested objects, output schema), the description covers all necessary aspects: partial vs full update, non-atomic behavior, experimental fields, and references to complementary tools. It is thoroughly complete.

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?

With 100% schema coverage, the description adds substantial meaning beyond the schema: it clarifies scoreFormat's display-only effect, partial merge behavior for anime/manga list options, full replace requirement for notificationOptions and disabledListActivity, and experimental warnings for certain fields. This far exceeds the baseline of 3.

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 states it updates settings on the authenticated user's own AniList account and lists specific fields (about, title language, adult-content visibility, etc.), clearly distinguishing from sibling tools that handle lists, threads, or activities.

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 explains when to use the tool (updating user settings) and provides important usage guidance: only set fields to change, warns about non-atomic behavior and the need to re-check with get_authorized_user on error. However, it does not explicitly state when not to use it or compare to alternatives.

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