Skip to main content
Glama
RichardGuan1

EH Index MCP

by RichardGuan1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get detailed gallery information

eh_get_gallery_detail
Read-onlyIdempotent

Retrieve a gallery's complete detail page: structured fields, grouped tags with strength, rating statistics, parent/newer versions, and the uploader's description.

Instructions

Read one gallery's detail page, including structured fields, grouped tags with strength, rating statistics, parent/newer versions, and the uploader-provided description as untrusted text. Use eh_get_gallery_metadata for authoritative API metadata in batches; use eh_get_gallery_comments for comments and eh_get_torrents for torrent records and URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoTarget site; gallery URLs override this when a URL is providede-hentai
galleryNoGallery ID and token; provide this or galleryUrl, but not both
galleryUrlNoFull gallery URL; provide this or gallery, but not both

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • 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"
  2. Changed2 schema fields changedv0.1.1
    • addedOutput schema / properties / result / properties / description
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "text": {
+          "type": "string"
+        },
+        "untrusted": {
+          "const": true,
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "text",
+        "untrusted"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / result / required
      Previous value: -[
-  "gallery",
-  "tagGroups",
-  "newerVersions"
-]New value: +[
+  "gallery",
+  "description",
+  "tagGroups",
+  "newerVersions"
+]
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds meaningful behavioral context by disclosing that the uploader-provided description is untrusted text and by specifying what data is included in the detail page, which helps the agent interpret results.

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 with no redundancy: the first sentence front-loads the tool's core function and deliverables, and the second sentence provides concise alternative routing. 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?

For a tool with a rich output schema, nested parameters, and many siblings, the description is complete: it states what the tool returns, flags the untrusted text caveat, and names the relevant alternatives. It leaves nothing critical unexplained for an agent to invoke it correctly.

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 every parameter is already documented in the schema, including the site enum, gallery object with gid/token, and galleryUrl. The description does not need to add parameter-level meaning; the baseline of 3 applies because it adds no extra semantics beyond the schema.

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?

The description uses a specific verb ('Read') with a clear resource ('one gallery's detail page') and lists the actual content returned: structured fields, grouped tags with strength, rating statistics, parent/newer versions, and uploader description. It also names sibling tools that serve different purposes, making differentiation easy.

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?

The description explicitly routes the agent to alternatives: eh_get_gallery_metadata for authoritative API metadata in batches, eh_get_gallery_comments for comments, and eh_get_torrents for torrent records and URLs. This gives clear when-to-use and when-not-to-use guidance beyond what the schema provides.

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

Deploy Server

Other Tools