EH Index MCP

Overview Schema Source Related Servers Discussions Admin

Get gallery metadata

eh_get_gallery_metadata

Read-onlyIdempotent

Retrieve structured E-Hentai metadata for 1-25 gallery IDs and tokens, including tags, ratings, file size, torrents, and version links.

Instructions

Get authoritative E-Hentai API metadata for 1-25 gallery references, including namespaced tags, ratings, file size, torrent metadata, and official parent/current-version links. Use this for structured metadata and version-chain inputs; use eh_get_gallery_detail for page-level fields, tag strength, or the uploader description.

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-25 gallery IDs and tokens to look up

Output Schema

TableJSON Schema

Name	Required	Description	Default
`galleries`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedv0.3.0Oct 3, 2026
- 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"
-}
```
Changed2 schema fields changedv0.1.2Aug 26, 2026
- addedInput schema / properties / galleries / description
```
Added value: +"1-25 gallery IDs and tokens to look up"
```
- 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

A4/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds that results are 'authoritative E-Hentai API' data, implying a canonical source, but says nothing about rate limits, ExHentai auth requirements, or partial-failure behavior when some of the 25 references are invalid. With annotations carrying most of the burden, a 3 fits.

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 sentences, zero filler. Scope and content come first, the routing guidance to the sibling second, so the most decision-relevant information 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?

With an output schema present, return-value detail is unnecessary, and annotations plus 100% schema coverage handle safety and inputs. The description covers scope and one alternative, leaving only the batch-variant disambiguation unaddressed for a tool in a large sibling cluster.

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 description coverage is 100% and the site enum, gid, and token constraints are all documented in the schema itself. The description only restates the 1-25 bound and does not clarify token format, site override precedence, or per-item error semantics. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('Get authoritative E-Hentai API metadata'), the batch scope (1-25 gallery references), and enumerates the returned content (namespaced tags, ratings, file size, torrent metadata, parent/current-version links). It explicitly positions itself against eh_get_gallery_detail, so an agent can separate the two without opening schemas.

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 a clear positive trigger ('structured metadata and version-chain inputs') and a named alternative with its own conditions ('use eh_get_gallery_detail for page-level fields, tag strength, or the uploader description'). It does not address the near-duplicate sibling eh_get_gallery_metadata_batch or the version-chain tools (eh_get_gallery_chain, eh_compare_gallery_versions), which is the main remaining ambiguity.

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