Kitsu

Top Anime

top_anime

Read-onlyIdempotent

Kitsu anime and manga database — the highest-ranked anime on Kitsu, ordered by popularityRank (default) or ratingRank, up to 20 entries. Each entry returns the Kitsu anime id, titles, both rank positions, average rating, episode count and synopsis. Answers which anime are most popular or highest rated according to Kitsu.

Input Schema

Name	Required	Description	Default
`by`	No	popularityRank (default) \| ratingRank
`limit`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "by": "ratingRank",
+    "limit": 20
+  },
+  {
+    "limit": 10
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Kitsu JSON:API response for top anime list",
+  "type": "object"
+}

First observedMay 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already indicate a safe, read-only, idempotent operation, so the bar is lower. The description adds valuable behavioral details: ordering options, a maximum of 20 entries, and the exact fields returned (id, titles, ranks, rating, episode count, synopsis). No contradictions with annotations.

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?

The description is two sentences, front-loaded with the core purpose. Every sentence adds value: the first defines the tool, the second details output and use cases. No redundancy or fluff.

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 simplicity, the description is complete. It covers what data is returned, possible orderings, and the maximum result count. With an output schema present, no further return-format details are needed.

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?

The schema covers only 50% of parameters, but the description compensates fully. It explains the 'by' parameter as 'popularityRank (default) or ratingRank' and the 'limit' parameter by stating 'up to 20 entries,' giving both meaning and constraints.

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 tool's function: returning the highest-ranked anime on Kitsu, ordered by popularityRank or ratingRank. It specifies the resource (Kitsu anime) and differentiates from siblings like search_anime and top_manga by focusing on ranking lists.

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 implies usage by saying 'Answers which anime are most popular or highest rated according to Kitsu,' providing clear context. However, it does not explicitly mention alternatives or when not to use the tool, though sibling names suggest the distinction.

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

All Kitsu tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.