AniList MCP Server

Overview Schema Source Related Servers Discussions Admin

Follow/unfollow a user

toggle_follow_user

Follow or unfollow an AniList user by their numeric ID. Toggle the follow status of a user on your account — call it again to reverse.

Instructions

[Requires login] Toggle following another AniList user from the authenticated user's account. Calling it again on the same user unfollows them.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	AniList numeric user ID to follow/unfollow — this mutation has no username form; resolve one via search_user or get_user_profile first.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`user`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.9.0Sep 27, 2026
- removedOutput schema / properties / user / properties / isFollowing / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / user / properties / isFollowing / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
- removedOutput schema / properties / user / properties / name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / user / properties / name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
Changed5 schema fields changedv0.7.1Aug 1, 2026
- addedInput schema / properties / id / exclusiveMinimum
```
Added value: +0
```
- removedInput schema / properties / id / minimum
```
Removed value: --2147483648
```
- addedOutput schema / properties / user / properties / id / exclusiveMinimum
```
Added value: +0
```
- changedOutput schema / properties / user / properties / id / maximum
```
Previous value: -9007199254740991New value: +2147483647
```
- removedOutput schema / properties / user / properties / id / minimum
```
Removed value: --9007199254740991
```
Addedv0.4.0Jul 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description meaningfully adds beyond annotations by disclosing the login requirement and the toggling behavior — calling again unfollows. This is important state-changing context that the annotations (readOnlyHint=false, idempotentHint=false) do not fully convey on their own.

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?

Two sentences with no filler. The login requirement is front-loaded, and the toggle/unfollow behavior is stated in one follow-up sentence. Every sentence earns its place.

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 single-parameter mutation with an output schema, the description plus the rich schema description fully cover what an agent needs: the action, auth requirement, toggle behavior, and how to identify the user. No important operational detail is missing.

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

Parameters3/5

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

Schema description coverage is 100%, and the schema already explains the numeric ID format, the absence of a username form, and the need to resolve via search_user or get_user_profile. The description adds no additional parameter-level meaning, so the baseline of 3 is appropriate.

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 uses a specific verb ('Toggle following') and names the exact resource (another AniList user from the authenticated account), going beyond the title to define the toggle behavior. This clearly distinguishes it from sibling tools like toggle_favourite or get_user_profile.

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 clearly establishes the context: login is required and the action operates on the authenticated user's account. It does not explicitly name alternatives or exclusions, but the tool's scope is narrow enough that the usage context is clear.

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

Deploy Server