EH Index MCP

Overview Schema Source Related Servers Discussions Admin

Get metadata for many galleries

eh_get_gallery_metadata_batch

Read-onlyIdempotent

Fetch official metadata for up to 500 E-Hentai or ExHentai galleries at once; server splits requests into 25-item API calls and returns ordered results with success and error counts.

Instructions

Get official metadata for up to 500 galleries. The server splits requests into official 25-item API batches and returns per-input results in order with input, success, and error counts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`site`	No	Target site; gallery URLs override this when a URL is provided	e-hentai
`galleries`	Yes	1-500 gallery IDs and tokens; results preserve input order

Output Schema

TableJSON Schema

Name	Required	Description	Default
`galleries`	Yes
`errorCount`	Yes
`inputCount`	Yes
`successCount`	Yes
`preservedOrder`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedv0.3.0Oct 3, 2026
- changedOutput schema / properties / errorCount / minimum
```
Previous value: -0New value: +-9007199254740991
```
- changedOutput schema / properties / galleries / items / additionalProperties
```
Previous value: -falseNew value: +{}
```
- removedOutput schema / properties / galleries / items / properties / category
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / current_gid
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / current_key
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / expunged
```
Removed value: -{
-  "type": "boolean"
-}
```
- removedOutput schema / properties / galleries / items / properties / filecount
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / filesize
```
Removed value: -{
-  "type": "number"
-}
```
- removedOutput schema / properties / galleries / items / properties / first_gid
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / first_key
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / gid / exclusiveMinimum
```
Removed value: -0
```
- removedOutput schema / properties / galleries / items / properties / gid / maximum
```
Removed value: -9007199254740991
```
- changedOutput schema / properties / galleries / items / properties / gid / type
```
Previous value: -"integer"New value: +"number"
```
- removedOutput schema / properties / galleries / items / properties / parent_gid
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / parent_key
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / posted
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / rating
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / tags
```
Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
```
- removedOutput schema / properties / galleries / items / properties / thumb
```
Removed value: -{
-  "format": "uri",
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / title
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / title_jpn
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / torrentcount
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / galleries / items / properties / torrents
```
Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "added": {
-        "type": "string"
-      },
-      "fsize": {
-        "type": "string"
-      },
-      "hash": {
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "tsize": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "hash",
-      "added",
-      "name",
-      "tsize",
-      "fsize"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
```
- removedOutput schema / properties / galleries / items / properties / uploader
```
Removed value: -{
-  "type": "string"
-}
```
- changedOutput schema / properties / inputCount / minimum
```
Previous value: -0New value: +-9007199254740991
```
- changedOutput schema / properties / successCount / minimum
```
Previous value: -0New value: +-9007199254740991
```

Changed5 schema fields changedv0.2.0Oct 2, 2026

addedOutput schema / properties / errorCount

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

addedOutput schema / properties / inputCount

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

addedOutput schema / properties / preservedOrder

Added value: +{
+  "const": true,
+  "type": "boolean"
+}

addedOutput schema / properties / successCount

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

changedOutput schema / required

Previous value: -[
-  "galleries"
-]New value: +[
+  "galleries",
+  "inputCount",
+  "successCount",
+  "errorCount",
+  "preservedOrder"
+]

Changed2 schema fields changedv0.1.2Aug 26, 2026

addedInput schema / properties / galleries / description

Added value: +"1-500 gallery IDs and tokens; results preserve input order"

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

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 safety is covered. The description adds genuinely useful behavior beyond that: server-side chunking into official 25-item API batches, preserved input order, and per-input success/error accounting, which tells the agent partial failures are possible and results are positional.

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 tight sentences, front-loaded with the scope and followed by the operational detail. No filler and nothing repeated from the title or schema.

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?

An output schema exists, so return values need not be re-explained, yet the description usefully previews the per-input result shape and counts. For a batch tool with nested item objects, this covers the key call-time concerns (limit, chunking, ordering, partial failure) without over-explaining.

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%, so both parameters (site enum and the galleries array with gid/token constraints) are already fully documented. The description reinforces the 500 cap and ordering but adds no format, validation, or default behavior beyond what the schema states, so the baseline 3 applies.

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 and resource ("Get official metadata") plus the distinguishing scope ("up to 500 galleries"), which cleanly separates it from the single-gallery sibling eh_get_gallery_metadata. It never names that sibling explicitly, so an agent must infer the batch-vs-single distinction from the name and count.

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 500-item ceiling and batching note imply this is the bulk path, but there is no explicit when-to-use guidance, no condition selecting it over eh_get_gallery_metadata or eh_resolve_gallery_batch, and no stated prerequisites (auth, site scoping). Usage is inferable rather than stated.

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