mcp-animenewsnetwork

Search the encyclopedia

search_titles

Read-onlyIdempotent

Search Anime News Network's encyclopedia by title to locate matching anime/manga entries. Returns compact rows with id, kind, type, and vintage; use the id and kind to retrieve full entries.

Instructions

Search the Anime News Network encyclopedia for anime and manga by title. Returns one compact row per match: id, kind, type, name, precision and vintage. Use the id and kind with get_title to read the full entry. Matching is on substring, so a short query returns a lot: narrow the query rather than raising 'limit'. This searches titles only. It cannot find an entry from a plot detail, a character or a studio.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	No	Restrict results to one kind. The encyclopedia returns both by default.	both
`limit`	No	How many rows to return.
`query`	Yes	Title or part of one, for example 'cowboy bebop'.

Output Schema

TableJSON Schema

Name	Required	Description
`notes`	Yes
`query`	Yes
`results`	Yes
`total_available`	Yes	Matches before 'limit' was applied. Higher than results.length means narrow the query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv2.0.0Aug 26, 2026
- addedOutput schema / properties / results / items / properties / id / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / results / items / properties / id / minimum
```
Added value: +-9007199254740991
```
- addedOutput schema / properties / results / items / properties / precision / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / results / items / properties / precision / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / results / items / properties / type / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / results / items / properties / type / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / results / items / properties / vintage / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / results / items / properties / vintage / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / total_available / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / total_available / minimum
```
Added value: +-9007199254740991
```
First observedv1.0.0Aug 4, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (readOnly, openWorld, idempotent, non-destructive), the description discloses important behavior: substring matching, compact row output with specific fields, and the fact that short queries return many results. This goes well beyond the structured metadata and gives the agent accurate expectations for calling the tool.

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 compact and front-loaded with the core purpose, followed by output details, usage guidance, and limitations. Every sentence contributes meaningful information without redundancy or filler.

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 search tool with full schema coverage, a rich output schema, and annotations covering safety and idempotence, the description is complete. It covers what the tool searches, what it returns, how to follow up with get_title, and what it cannot do, leaving no critical gap for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already covers all parameters at 100%, providing descriptions for query, kind, and limit. The description adds extra semantic value by explaining substring matching and advising to narrow the query rather than increase the limit, which helps the agent use query and limit more effectively.

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: 'Search the Anime News Network encyclopedia for anime and manga by title.' It also explicitly distinguishes this tool from get_title by saying to use the returned id and kind with get_title for the full entry, and clarifies that it cannot find entries by plot, character, or studio.

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?

The description gives clear when-to-use guidance: title-based lookups only, with a follow-up call to get_title using the returned id and kind. It also provides practical advice to narrow the query rather than raising 'limit' and explicitly states the tool's limitations relative to plot, character, and studio searches.

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

Deploy Server