EH Index MCP

Overview Schema Source Related Servers Discussions Admin

Search E-Hentai galleries

eh_search_galleries

Read-onlyIdempotent

Search E-Hentai or ExHentai galleries by title, native tags, category, rating, page count, torrent, expunged status, and cursor filters; resolve translated tags first when needed.

Instructions

Search E-Hentai or ExHentai with native title and tag syntax plus optional category, rating, page-count, torrent, expunged, and cursor filters. Use namespace-qualified tags such as artist:name or female:tag when needed. For translated Chinese or English tag names, resolve the native tag token with eh_search_translated_tags first; native tags can be passed directly.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`next`	No	Next-page cursor returned by this tool
`prev`	No	Previous-page cursor returned by this tool
`seek`	No	E-Hentai seek value, such as a date or gallery ID
`site`	No	Target site; gallery URLs override this when a URL is provided	e-hentai
`query`	No	Native E-Hentai query, e.g. language:chinese$ artist:name$
`pageTo`	No	One-based last result page to scan
`pageFrom`	No	One-based first result page to scan
`minRating`	No	Minimum rating from 2 through 5
`categories`	No	Gallery categories to include; omit to use all categories
`hasTorrent`	No	When true, require galleries with torrent metadata
`browseExpunged`	No	When true, include expunged galleries where supported
`disableTagFilter`	No	Disable the site's default tag filtering
`disableLanguageFilter`	No	Disable the site's default language filtering
`disableUploaderFilter`	No	Disable the site's default uploader filtering

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.0Oct 2, 2026

addedOutput schema / properties / result / properties / galleries / items / properties / site

Added value: +{
+  "enum": [
+    "e-hentai",
+    "exhentai"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / result / properties / galleries / items / required

Previous value: -[
-  "gid",
-  "token",
-  "url",
-  "title",
-  "category",
-  "uploader",
-  "posted",
-  "pages",
-  "rating",
-  "tags",
-  "thumbnailUrl"
-]New value: +[
+  "gid",
+  "token",
+  "site",
+  "url",
+  "title",
+  "category",
+  "uploader",
+  "posted",
+  "pages",
+  "rating",
+  "tags",
+  "thumbnailUrl"
+]

Changed10 schema fields changedv0.1.2Aug 26, 2026

addedInput schema / properties / browseExpunged / description

Added value: +"When true, include expunged galleries where supported"

addedInput schema / properties / categories / description

Added value: +"Gallery categories to include; omit to use all categories"

addedInput schema / properties / disableLanguageFilter / description
```
Added value: +"Disable the site's default language filtering"
```
addedInput schema / properties / disableTagFilter / description
```
Added value: +"Disable the site's default tag filtering"
```
addedInput schema / properties / disableUploaderFilter / description
```
Added value: +"Disable the site's default uploader filtering"
```

addedInput schema / properties / hasTorrent / description

Added value: +"When true, require galleries with torrent metadata"

addedInput schema / properties / minRating / description
```
Added value: +"Minimum rating from 2 through 5"
```
addedInput schema / properties / pageFrom / description
```
Added value: +"One-based first result page to scan"
```

addedInput schema / properties / pageTo / description

Added value: +"One-based last result page to scan"

addedInput schema / properties / site / description

Added value: +"Target site; gallery URLs override this when a URL is provided"

First observedv0.1.0Aug 18, 2026

TDQS

A3.8/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 the safety profile is covered. The description adds the tag-syntax prerequisite and mentions cursor filters, but says nothing about pagination/return behavior beyond the schema. With annotations carrying the load, this is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core capability and then the two practical usage notes. No filler, though the tag-syntax sentence could be slightly tighter.

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?

With a rich output schema, full annotation coverage and 100% parameter documentation, the description rounds out the definition by explaining query syntax and tag resolution. Nothing essential to call it correctly appears missing.

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 100%, so the baseline is 3, but the description adds real value by explaining namespace-qualified tag syntax (artist:name, female:tag) and the native-vs-translated token distinction, which the schema does not elaborate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (search galleries on E-Hentai or ExHentai) and enumerates the filter families it supports. It distinguishes itself from eh_search_translated_tags by routing tag-name resolution there, but does not differentiate from the many other search siblings (batch, watched, by_hash, favorites).

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?

Gives explicit routing guidance: resolve translated Chinese/English tag names with eh_search_translated_tags first, while native tags can be passed directly. It lacks any when-not conditions (e.g., when to prefer batch or hash search), so it stops short of a 5.

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