Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

webtoon_genre

Lists every WEBTOON series in a chosen genre, returning titles, authors, thumbnails, canonical URLs, counters, and UP badges, with optional sort order for browsing or research.

Instructions

List every series in one WEBTOON genre. Returns one WEBTOON (webtoons.com) genre listing: every series the site lists for that genre in one document, with each series' title number, title, genre label, authors when the card prints them, thumbnail, canonical URL, the site's own counter and the UP badge. The response carries the site's own series total for the genre when the page prints it. Genres come from webtoon-genres; sort is WEBTOON's own ordering control.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "genre": "<genre>"
    },
    "name": "webtoon_genre"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoResult ordering
genreYesGenre slug from webtoon-genres

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that the response is a single complete document (no pagination) and enumerates the returned fields including the site counter and UP badge, but it says nothing about auth, rate limits, or failure behavior for an invalid genre slug.

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?

Purpose is front-loaded in the first sentence and the rest is field-level detail with little filler. The clause 'every series the site lists for that genre in one document' slightly restates the opening, but overall it stays tight.

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?

With no output schema and no annotations, the description does the work of enumerating the returned fields and noting the site total and UP badge. It covers enough for an agent to invoke and interpret results correctly, missing only edge-case behavior.

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 coverage is 100% and both parameters are enums already documented in the schema. The description adds only marginal meaning: it points to webtoon_genres as the source of the genre value and characterizes sort as the site's own ordering, without explaining what MANA/LIKEIT/UPDATE actually mean.

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?

Opens with a specific verb and resource ('List every series in one WEBTOON genre') and immediately constrains scope to a single genre. It distinguishes itself from the genre-catalog sibling by noting 'Genres come from webtoon-genres', so an agent can tell it apart without opening a schema.

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

Usage Guidelines3/5

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

It implies a workflow — fetch a genre slug from webtoon_genres first — and notes that 'sort is WEBTOON's own ordering control'. But it never states when to prefer this over webtoon_search or webtoon_series, nor any exclusions, so the guidance is implied rather than explicit.

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