EH Index MCP

Overview Schema Source Related Servers Discussions Admin

Search and organize gallery works

eh_search_gallery_works

Read-onlyIdempotent

Search E-Hentai/ExHentai galleries, merge official versions and variants into works, and group installments into series with confidence levels and source galleries.

Instructions

Search up to 10 result pages, fetch official metadata, merge official version links and likely language/upload variants into works, then group installments into series. galleryCount counts unique gallery uploads; uniqueWorkCount is heuristic and every work includes a confidence level plus all source galleries.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`next`	No	Resume cursor returned by a previous truncated work search
`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
`maxPages`	No	Maximum result pages to scan; each page consumes one rate-limited search request
`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.

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"

Changed3 schema fields changedv0.1.1Aug 24, 2026

added

Output schema / properties / result / properties / series / items / properties / works / items / properties / groupingBasis

Added value: +{
+  "enum": [
+    "official-version-chain",
+    "normalized-title-and-creator",
+    "standalone"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / result / properties / series / items / properties / works / items / properties / groupingExplanation
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / result / properties / series / items / properties / works / items / required

Previous value: -[
-  "key",
-  "title",
-  "installment",
-  "creators",
-  "availableLanguages",
-  "groupingConfidence",
-  "preferredGallery",
-  "variants"
-]New value: +[
+  "key",
+  "title",
+  "installment",
+  "creators",
+  "availableLanguages",
+  "groupingConfidence",
+  "groupingBasis",
+  "groupingExplanation",
+  "preferredGallery",
+  "variants"
+]

First observedv0.1.0Aug 18, 2026

TDQS

A4/5.0

Behavior5/5

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

While annotations already declare read-only, idempotent, and non-destructive behavior, the description adds important non-obvious semantics: galleryCount counts unique gallery uploads, uniqueWorkCount is heuristic, and every work carries a confidence level plus all source galleries. This prevents the agent from misinterpreting counts or treating merged works as true deduplicated entities.

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?

Two dense sentences communicate the full pipeline and the two key count semantics without redundant filler. The most important scoping information ('up to 10 result pages') is front-loaded.

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?

Given the 13-parameter schema, full schema coverage, output schema, and strong annotations, the description is sufficient for an agent to understand the tool's high-level behavior and output quirks. It could be slightly more complete by explicitly mentioning pagination/truncation via the next cursor, but the schema and the 'up to 10 result pages' phrase cover the essentials.

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?

The input schema covers 100% of parameters with descriptions, so the baseline of 3 applies. The description does not elaborate on individual parameters, but it clarifies output count semantics that relate indirectly to how aggregation behaves.

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?

The description states a specific multi-step behavior: search up to 10 result pages, merge official version/language/upload variants into works, and group installments into series. This clearly communicates a gallery-work aggregation tool, though it does not explicitly compare itself with sibling search tools like eh_search_galleries.

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

Usage Guidelines3/5

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

The intended use is implied: choose this tool when you want aggregated 'works' and series rather than raw gallery results, and when up to 10 pages of scanning is acceptable. However, it never states when not to use it or names alternative sibling tools for raw gallery search or batch operations.

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