mcp-animenewsnetwork

Search the encyclopedia

search_titles

Read-onlyIdempotent

Search Anime News Network anime and manga encyclopedia entries by title substring and return compact matches with IDs and kinds. Use the returned ID and kind with get_title to read full details.

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

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

Name	Required	Description
`notes`	Yes
`query`	Yes
`results`	Yes
`total_available`	Yes	Rows this server could read, before 'limit' was applied. Higher than results.length means narrow the query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv3.0.0Oct 30, 2026

removedOutput schema / properties / results / items / properties / precision / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / precision / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / results / items / properties / type / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / type / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / results / items / properties / vintage / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / results / items / properties / vintage / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / total_available / description

Previous value: -"Matches before 'limit' was applied. Higher than results.length means narrow the query."New value: +"Rows this server could read, before 'limit' was applied. Higher than results.length means narrow the query."

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, the description discloses that matching is substring-based, that short queries return many results, and what columns are returned per match. This gives the agent useful behavioral context for forming queries and interpreting results.

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 front-loaded with purpose and return shape, then adds usage guidance and limitations. Every sentence contributes practical information for selecting and invoking the tool.

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 search behavior, output schema, and sibling tools, the description is complete enough to call correctly. It explains what the rows contain, how to continue with get_title, and the important scope limitation that this is title-only search.

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?

Schema coverage is already 100%, so the baseline is 3. The description adds meaningful query semantics: matching is substring-based, short queries are broad, and the recommended strategy is to narrow the query rather than increase limit.

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 titles. It distinguishes itself from get_title by explaining that search returns compact rows and that get_title should be used for full entries, and it clarifies that it searches titles only.

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?

It explicitly explains when to use this tool, how to follow up with get_title using id and kind, and how to handle broad results by narrowing the query rather than raising limit. It also states what the tool cannot do, including finding entries from plot details, characters, or studios.

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

Deploy Server