AniList MCP Server

Overview Schema Source Related Servers Discussions Admin

Follow/unfollow a user

toggle_follow_user

Follow or unfollow an AniList user from your authenticated account by toggling the follow state for a numeric user ID.

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

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

Name	Required	Description	Default
`user`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.11.0Oct 25, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
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 annotations already indicate a non-read-only, non-idempotent, open-world mutation. The description adds useful context beyond that by stating login is required and explaining that a second call on the same user unfollows them.

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 tightly written sentences with no waste. The login requirement is front-loaded, and the toggle behavior is immediately clear.

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 toggle mutation with annotations and an output schema, the definition is complete enough. Authentication, mutation behavior, and repeat-call semantics are all covered.

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 coverage is 100%, and the schema itself explains that the id is a numeric AniList user ID with no username form. The description adds no parameter meaning beyond what the schema already provides, so the baseline of 3 applies.

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 a specific verb and resource: toggling following for another AniList user from the authenticated account. It is easy to distinguish from read-only user tools and from other mutations in the sibling list.

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 clearly establishes the usage context: login is required, and the toggle applies to another AniList user from the authenticated account. It notes repeat-call behavior but does not explicitly name alternatives or exclusions.

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

Deploy Server