EH Index MCP

Overview Schema Source Related Servers Discussions Admin

Search galleries across pages

eh_search_galleries_batch

Read-onlyIdempotent

Search up to 10 result pages in one call, deduplicate gallery references, and return a resume cursor when the page budget truncates the scan.

Instructions

Search up to 10 result pages without metadata expansion, deduplicate gallery references, and return a resume cursor when the page budget truncates the scan.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`next`	No	Resume cursor returned by a previous truncated batch 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
`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.

Changed6 schema fields changedv0.2.0Oct 2, 2026

addedOutput schema / properties / result / properties / errorCount
```
Added value: +{
+  "const": 0,
+  "type": "number"
+}
```

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"
+]

addedOutput schema / properties / result / properties / inputCount

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedOutput schema / properties / result / properties / preservedOrder
```
Added value: +{
+  "const": true,
+  "type": "boolean"
+}
```

changedOutput schema / properties / result / required

Previous value: -[
-  "galleries",
-  "pagesScanned",
-  "resultCount",
-  "truncated",
-  "next"
-]New value: +[
+  "galleries",
+  "inputCount",
+  "pagesScanned",
+  "resultCount",
+  "errorCount",
+  "preservedOrder",
+  "truncated",
+  "next"
+]

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"

Addedv0.1.1Aug 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: a 10-page budget cap, deduplication of gallery references, and a resume cursor emitted when truncation occurs.

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?

A single front-loaded sentence with no filler; the scan scope, the dedup behavior, and the truncation/resume semantics each carry distinct information.

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 an output schema present the return shape need not be explained, and 100% schema coverage plus annotations cover parameters and safety. The only real shortfall is absent routing guidance versus the sibling search tools.

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 coverage is 100% with 13 documented parameters, so the schema does the heavy lifting and a 3 is the baseline. The description only loosely maps to two of them (page budget → maxPages, resume cursor → next) and adds no syntax or filtering guidance beyond the schema.

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 (batch gallery search across up to 10 pages) plus the differentiating behaviors: no metadata expansion, deduplication, and resume cursor. An agent can distinguish it from single-page search and the metadata-batch sibling, though no sibling is named explicitly.

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?

Usage is implied rather than spelled out: 'without metadata expansion' hints that metadata-batch tools are the alternative, and the page-budget framing implies bulk scanning. There is no explicit when-to-use/when-not statement or named alternative.

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