Skip to main content
Glama

zerochan_get_entry

Read-onlyIdempotent

Retrieve detailed metadata for a ZeroChan anime image post using its numeric ID, including tags, image URLs, dimensions, and associated categories.

Instructions

Retrieve detailed information about a single Zerochan entry by its numeric ID.

Returns full metadata including all tags, image URLs (full/medium/small),
source, dimensions, favorites, and associated anime/manga/game categories.

Args:
    params (GetEntryInput): Input parameters including:
        - username (str): Your Zerochan username (required)
        - entry_id (int): Numeric ID of the Zerochan post (e.g. 3793685)
        - response_format (ResponseFormat): 'markdown' or 'json' (default: 'markdown')

Returns:
    str: Detailed entry data in the requested format.
         Markdown: formatted card with all metadata, tag list, and image URLs.
         JSON: complete raw API response with all available fields.

Schema (JSON):
    {
        "id": int,
        "primary": str,           # Primary/main tag for this image
        "tags": list[str],         # All associated tags
        "width": int,
        "height": int,
        "fav": int,                # Favorite/popularity count
        "source": str,             # Original source URL if available
        "full": str,               # Direct URL to full resolution image
        "medium": str,             # Medium preview URL
        "small": str,              # Small thumbnail URL
        "anime": str | null,       # Associated anime title if any
        "manga": str | null,
        "game": str | null
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate this is a read-only, non-destructive, idempotent, and open-world operation. The description adds valuable context by detailing what metadata is returned (tags, image URLs, categories) and the output format options (markdown vs. JSON), which goes beyond the annotations. No contradictions with annotations are present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (purpose, returns, args, schema), but includes redundant schema details that are already in the output schema. It could be more concise by omitting the schema duplication, though the information is front-loaded and each sentence adds value.

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?

Given the tool's complexity, rich annotations, and the presence of an output schema, the description is complete. It covers purpose, parameters, return values, and behavioral details, making it sufficient for an agent to understand and invoke the tool correctly without needing additional explanation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, but the description compensates by explaining the parameters in the 'Args' section, including 'entry_id' (numeric ID), 'response_format' (markdown/json), and notes on defaults. However, it incorrectly lists 'username' as required when the schema does not include it, causing a minor inconsistency.

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 clearly states the specific action ('Retrieve detailed information') and resource ('about a single Zerochan entry by its numeric ID'), distinguishing it from sibling tools like 'zerochan_browse' and 'zerochan_search' which likely handle multiple entries or search queries rather than single-entry retrieval.

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?

The description implies usage context by specifying it's for retrieving detailed information about a single entry, which naturally contrasts with browsing or searching multiple entries. However, it does not explicitly state when to use this tool versus its siblings or mention any exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/citronlegacy/zerochan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server