trending_animeGet currently trending anime ranked by popularity. Returns title, status, score, episode count, and genres. Use get_anime with the ID for full details.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of results to return (1–25, default 10) |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | Number of results returned | |
| results | Yes | Array of trending anime results |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "count": {
+ "description": "Number of results returned",
+ "type": "number"
+ },
+ "results": {
+ "description": "Array of trending anime results",
+ "items": {
+ "properties": {
+ "average_score": {
+ "description": "Average community score (0-100)",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "cover_image": {
+ "description": "URL to cover image",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "description": {
+ "description": "Anime synopsis/description",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "duration_minutes": {
+ "description": "Episode duration in minutes",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "episodes": {
+ "description": "Total episode count",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "favourites": {
+ "description": "Number of times added to favorites",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "format": {
+ "description": "Anime format (TV, MOVIE, OVA, ONA, SPECIAL)",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "genres": {
+ "description": "List of genres",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "id": {
+ "description": "AniList media ID",
+ "type": "number"
+ },
+ "mean_score": {
+ "description": "Mean community score (0-100)",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "popularity": {
+ "description": "Popularity ranking",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "season": {
+ "description": "Season aired (SPRING, SUMMER, FALL, WINTER)",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "season_year": {
+ "description": "Year of airing season",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "site_url": {
+ "description": "AniList page URL",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "source": {
+ "description": "Original source (MANGA, LIGHT_NOVEL, VISUAL_NOVEL, etc)",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "description": "Current status (FINISHED, AIRING, NOT_YET_AIRED, CANCELLED)",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "studios": {
+ "description": "List of animation studio names",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "title_english": {
+ "description": "Anime title in English",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "title_native": {
+ "description": "Anime title in native language",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "title_romaji": {
+ "description": "Anime title in Romaji",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "id",
+ "title_romaji",
+ "title_english",
+ "title_native",
+ "description",
+ "episodes",
+ "duration_minutes",
+ "status",
+ "format",
+ "source",
+ "season",
+ "season_year",
+ "average_score",
+ "mean_score",
+ "popularity",
+ "favourites",
+ "genres",
+ "cover_image",
+ "site_url",
+ "studios"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "count",
+ "results"
+ ],
+ "type": "object"
+}Input schema / examplesAdded value: +[
+ {
+ "limit": 10
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that results are 'currently trending' and 'ranked by popularity', but does not disclose additional behavioral traits like freshness or pagination. No contradiction 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences: the first provides purpose and output, the second gives usage guidance. No wasted words, well-structured.
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 simple list tool with one optional parameter, clear annotations, and an output schema, the description covers the purpose, output, and provides a link to the sibling tool. Complete enough.
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?
Schema coverage is 100% for the single parameter 'limit', which has a clear description. The tool description does not add extra parameter details beyond the schema, so baseline 3 is appropriate.
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?
The description clearly states the verb 'Get', the resource 'currently trending anime ranked by popularity', and specifies the returned fields. It distinguishes itself from the sibling tool 'get_anime' by advising to use that for full details.
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?
The description provides explicit guidance on when to use the alternative tool 'get_anime' for full details, implying this tool is for summary/overview. It does not state when not to use it, but the context is clear for a simple trending list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.