get_genresLists every genre name AniList uses to tag anime/manga. Call before filtering search_media by genre to ensure you pass a recognized genre name.
List every genre name AniList uses to tag anime/manga (e.g. Action, Comedy, Slice of Life). Call this before filtering search_media by genre, so you pass a name AniList actually recognizes.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| genres | Yes |
Changes observed during successful MCP inspections.
v0.11.0Input schema / additionalPropertiesAdded value: +falsev0.3.0v0.2.0v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context: this is a canonical reference list whose values are required for valid genre filtering. It does not discuss result size or formatting, but the output schema covers return values.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the purpose and followed immediately by the usage instruction and rationale. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter reference tool with annotations and an output schema, this is complete. An agent knows what it returns, why to call it, and when it should be used ahead of genre-filtered searches.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4; there are no parameter semantics for the description to clarify. The description appropriately focuses on the tool's role rather than inventing parameter guidance.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a precise verb and resource: listing every genre name AniList uses to tag anime/manga. The examples (Action, Comedy, Slice of Life) and the mention of AniList's own vocabulary distinguish it from sibling tools like get_media_tags and search_media.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says to call this before filtering search_media by genre and explains why: so the caller passes a name AniList actually recognizes. That gives both a trigger and the alternative context an agent needs.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.