EH Index MCP

Overview Schema Source Related Servers Discussions Admin

Find latest gallery version

eh_find_latest_gallery_version

Read-onlyIdempotent

Resolve a gallery's official and detail-page version chain, then return its highest semantic version. Use it to check which release is current for a gallery ID, token, or URL.

Instructions

Resolve one gallery's official and detail-page version chain, then return the latest semantic version. Use eh_get_gallery_chain when the complete ordered chain is needed. Invalid references, deleted galleries, authentication failures, challenge pages, and upstream errors are returned as tool errors.

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
`gallery`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedv0.3.0Oct 3, 2026
- changedOutput schema / properties / gallery / additionalProperties
```
Previous value: -falseNew value: +{}
```
- removedOutput schema / properties / gallery / properties / category
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / current_gid
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / current_key
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / expunged
```
Removed value: -{
-  "type": "boolean"
-}
```
- removedOutput schema / properties / gallery / properties / filecount
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / filesize
```
Removed value: -{
-  "type": "number"
-}
```
- removedOutput schema / properties / gallery / properties / first_gid
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / first_key
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / gid / exclusiveMinimum
```
Removed value: -0
```
- removedOutput schema / properties / gallery / properties / gid / maximum
```
Removed value: -9007199254740991
```
- changedOutput schema / properties / gallery / properties / gid / type
```
Previous value: -"integer"New value: +"number"
```
- removedOutput schema / properties / gallery / properties / parent_gid
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / parent_key
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / posted
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / rating
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / tags
```
Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
```
- removedOutput schema / properties / gallery / properties / thumb
```
Removed value: -{
-  "format": "uri",
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / title
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / title_jpn
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / properties / torrentcount
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / gallery / 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 / gallery / 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/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely useful failure context — invalid references, deleted galleries, auth failures, challenge pages, and upstream errors surface as tool errors — which an agent needs to handle outcomes.

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 waste: the core action is front-loaded, the routing alternative follows, and the error contract closes it out. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, sibling routing, and error modes, while an output schema exists so return values need not be explained. Nothing an agent needs to call this correctly is missing.

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%, with clear docs including the mutually-exclusive gallery vs galleryUrl constraint, so the schema carries parameter meaning. The description adds no additional parameter semantics, making the baseline 3 appropriate.

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: resolve a gallery's version chain and return the latest semantic version. It explicitly distinguishes itself from eh_get_gallery_chain, the closest sibling, so an agent can route correctly without inspecting schemas.

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

Usage Guidelines5/5

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

Gives both the when-to-use-this (need only the latest semver) and the explicit alternative with its selecting condition ('Use eh_get_gallery_chain when the complete ordered chain is needed'). Nothing is left to inference.

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