Skip to main content
Glama

Anilist Search Anime

anilist_search_anime
Read-onlyIdempotent

Search for anime by title. Returns title, episode count, status, score, genres, and synopsis. Use get_anime with the ID for full details.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "Attack on Titan"
    },
    "name": "anilist_search_anime"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (1-25, default 10)
queryYesAnime title to search for, e.g. "Attack on Titan" or "Cowboy Bebop"

Output Schema

NameRequiredDescriptionDefault
countYesNumber of results returned
resultsYesArray of anime search results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results to return (1–25, default 10)"New value: +"Number of results to return (1-25, default 10)"
  2. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and side-effect behavior is fully covered structurally. The description adds only the result field list, which duplicates the output schema, and says nothing about pagination, rate limits, or how matching works (fuzzy vs exact title).

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?

Three short sentences, front-loaded with purpose and result shape, ending with the routing hint. Every sentence carries a distinct function with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with an output schema and full annotation coverage, the description covers purpose, result shape, and next step. The slight redundancy of listing return fields already documented in the output schema keeps it from a 5.

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% with per-parameter descriptions and examples for both query and limit, so the schema carries the load. The description adds no meaning beyond it, making the baseline 3 correct.

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?

States a specific verb and resource ('Search for anime by title') and immediately distinguishes itself from the sibling anilist_get_anime by assigning full-detail retrieval to that tool. An agent can pick between search and get without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative explicitly ('Use get_anime with the ID for full details') and states the condition that selects it, creating a clear search-then-fetch flow. No inference is required about which tool to call first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.