EH Index MCP

Overview Schema Source Related Servers Discussions Admin

Get gallery version chain

eh_get_gallery_chain

Read-onlyIdempotent

Build an ordered, deduplicated version chain for an E-Hentai or ExHentai gallery by merging API version metadata with detail-page newer-version links from a gallery ID/token or URL.

Instructions

Combine official API version-chain metadata with detail-page newer-version links into an ordered, deduplicated gallery version list. Provide exactly one gallery reference or full gallery URL. Deleted galleries, malformed URLs, authentication failures, challenge pages, and upstream request errors are returned as tool errors rather than silently treated as an empty chain.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`site`	No	Target site; gallery URLs override this when a URL is provided	e-hentai
`gallery`	No	Gallery ID and token; provide this or galleryUrl, but not both
`galleryUrl`	No	Full gallery URL; provide this or gallery, but not both

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"
-}
```

Changed3 schema fields changedv0.1.2Aug 26, 2026

addedInput schema / properties / gallery / description

Added value: +"Gallery ID and token; provide this or galleryUrl, but not both"

addedInput schema / properties / galleryUrl / description

Added value: +"Full gallery URL; provide this or gallery, but not both"

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

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 goes further by disclosing the failure contract: deleted galleries, malformed URLs, auth failures, challenge pages and upstream errors surface as tool errors rather than a silent empty chain, which is exactly the kind of context annotations cannot convey.

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: the first delivers the behavior, the second delivers the input contract and error semantics. The most important 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 values need no explanation, and the description covers inputs and error behavior. The only omission is explicit guidance on choosing this tool over its version-related siblings, a minor gap for a well-annotated read tool.

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%, so both the site enum and the gallery/galleryUrl mutual exclusivity are already documented in the schema. The description restates the one-of constraint but adds no format or precedence detail beyond it, so the baseline 3 applies.

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 combination: it merges official API version-chain metadata with detail-page newer-version links into one ordered, deduplicated list. That scope cleanly separates it from siblings like eh_find_latest_gallery_version and eh_compare_gallery_versions without needing to name them.

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 only usage guidance is the input constraint that exactly one gallery reference or URL must be supplied. There is no explicit statement of when to reach for this tool versus the neighboring version-related tools, leaving the routing decision to inference from the purpose sentence.

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