Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

webtoon_genres

Lists WEBTOON's complete 17-genre taxonomy with slugs, labels, and listing URLs, so callers can discover genre values and avoid hard-coding them.

Instructions

List WEBTOON's complete genre taxonomy. Returns the complete WEBTOON (webtoons.com) genre list: 17 genres, each with its slug (pass it to webtoon-genre), display label and listing URL. This is the discovery endpoint for the genre parameter, so a caller never has to hard-code the set.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "webtoon_genres"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well for a read-only listing: it discloses the result cardinality (17 genres) and the fields returned (slug, label, listing URL). It does not address caching/staticness or failure behavior, which is the only remaining gap and is minor for a fixed taxonomy.

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?

Three short sentences, front-loaded with the purpose before the return detail and the caller-facing rationale. The final clause about never hard-coding the set slightly restates the discovery-endpoint point, but it is a single clause and does add a reason.

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?

There is no output schema, so the description must describe the return value, and it does: count plus per-entry fields. With no parameters and no annotations, this is close to complete; only the static/authoritative nature of the list goes unstated.

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 tool takes no parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description usefully redirects the reader from the absent input to the output field that matters as an input elsewhere (the slug).

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 opens with a specific verb+resource ('List WEBTOON's complete genre taxonomy') and then enumerates exactly what each entry contains: slug, display label, and listing URL. It is clearly distinguishable from the sibling webtoon_genre, which is named as the consumer of the slugs returned here.

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?

It states the operational role explicitly — 'the discovery endpoint for the genre parameter' — and tells the caller to pass the returned slug to webtoon-genre, which is the correct follow-on call. There is no explicit when-not-to-use clause, but for a zero-parameter static listing the practical guidance is effectively complete.

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