EH Index MCP

Overview Schema Source Related Servers Discussions Admin

Search watched-tag galleries

eh_search_watched

Read-onlyIdempotent

Search your authenticated watched-tag gallery feed with native queries, categories, advanced filters, and cursor pagination. Read-only; it does not modify watched tags or account settings.

Instructions

Read the authenticated user's watched-tag gallery feed with native search, category, advanced-filter, and cursor controls. This tool never changes watched tags or account settings.

Input Schema

Name	Required	Description	Default
`next`	No	Next-page cursor returned by this tool
`prev`	No	Previous-page cursor returned by this tool
`seek`	No	E-Hentai seek value, such as a date or gallery ID
`site`	No	Target site; gallery URLs override this when a URL is provided	e-hentai
`query`	No	Native E-Hentai query, e.g. language:chinese$ artist:name$
`pageTo`	No	One-based last result page to scan
`pageFrom`	No	One-based first result page to scan
`minRating`	No	Minimum rating from 2 through 5
`categories`	No	Gallery categories to include; omit to use all categories
`hasTorrent`	No	When true, require galleries with torrent metadata
`browseExpunged`	No	When true, include expunged galleries where supported
`disableTagFilter`	No	Disable the site's default tag filtering
`disableLanguageFilter`	No	Disable the site's default language filtering
`disableUploaderFilter`	No	Disable the site's default uploader filtering

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.0Oct 2, 2026

addedOutput schema / properties / result / properties / galleries / items / properties / site

Added value: +{
+  "enum": [
+    "e-hentai",
+    "exhentai"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / result / properties / galleries / items / required

Previous value: -[
-  "gid",
-  "token",
-  "url",
-  "title",
-  "category",
-  "uploader",
-  "posted",
-  "pages",
-  "rating",
-  "tags",
-  "thumbnailUrl"
-]New value: +[
+  "gid",
+  "token",
+  "site",
+  "url",
+  "title",
+  "category",
+  "uploader",
+  "posted",
+  "pages",
+  "rating",
+  "tags",
+  "thumbnailUrl"
+]

Changed10 schema fields changedv0.1.2Aug 26, 2026

addedInput schema / properties / browseExpunged / description

Added value: +"When true, include expunged galleries where supported"

addedInput schema / properties / categories / description

Added value: +"Gallery categories to include; omit to use all categories"

addedInput schema / properties / disableLanguageFilter / description
```
Added value: +"Disable the site's default language filtering"
```
addedInput schema / properties / disableTagFilter / description
```
Added value: +"Disable the site's default tag filtering"
```
addedInput schema / properties / disableUploaderFilter / description
```
Added value: +"Disable the site's default uploader filtering"
```

addedInput schema / properties / hasTorrent / description

Added value: +"When true, require galleries with torrent metadata"

addedInput schema / properties / minRating / description
```
Added value: +"Minimum rating from 2 through 5"
```
addedInput schema / properties / pageFrom / description
```
Added value: +"One-based first result page to scan"
```

addedInput schema / properties / pageTo / description

Added value: +"One-based last result page to scan"

addedInput schema / properties / site / description

Added value: +"Target site; gallery URLs override this when a URL is provided"

Addedv0.1.1Aug 24, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the closing sentence largely restates what structured data provides. It does add one genuinely new trait — the feed is scoped to the authenticated user — but omits pagination/cursor behavior, result ordering, or rate considerations, keeping it at a baseline-plus level.

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, both front-loaded with the operative noun phrase ('watched-tag gallery feed') and the safety boundary. Nothing is repeated and there is no filler.

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?

For a read-only, cursor-paged search tool with full annotation coverage, an output schema, and 100% schema documentation, the description covers the essentials: scope (watched tags), operation type (read), and auth requirement. The missing piece is routing against the many sibling search tools, which leaves a small gap.

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 every one of the 14 parameters carries its own description, including the enum for site and the category list. The description's phrase 'native search, category, advanced-filter, and cursor controls' only loosely groups those parameters and adds no syntax or format detail beyond the schema, 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 ('Read') and a precise resource ('watched-tag gallery feed'), and enumerates the functional scope (native search, categories, advanced filters, cursor controls). This distinguishes it implicitly from eh_search_favorites and eh_search_galleries, though it never names a sibling to make the boundary explicit.

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

Usage Guidelines2/5

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

The description gives no guidance on when to choose this over eh_search_galleries, eh_search_favorites, or the batch variants. The only conditional statement ('never changes watched tags') is a safety reassurance, not a usage rule, so the agent must infer selection criteria from the name alone.

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