Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

webtoon_series

Retrieve a WEBTOON title profile with metadata, counters, release day, and a ten-episode page list. Pass a title_no from any listing card to fetch episodes and detect further pages.

Instructions

Get a WEBTOON series with a page of its episode list. Returns one WEBTOON (webtoons.com) series: title, genre, authors, summary, cover, the site's own view and subscribe counters, the release-day line, and a ten-episode page window (episode number, title, release date, thumbnail, viewer URL, UP badge). Take title_no from any listing endpoint's card. The page window is fixed at ten episodes and WEBTOON publishes no total episode count, so has_next_page is a window-size signal, not an exact remaining count. An unknown title number is a 404. Panel images and Fast Pass state are never returned.

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": {
      "title_no": "<title_no>"
    },
    "name": "webtoon_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based episode page, ten episodes per page; defaults to 1
title_noYesWEBTOON title number from any listing card

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and mostly does: it declares the 404 behavior for unknown title numbers, discloses that WEBTOON publishes no total episode count (so has_next_page is a window signal, not a remaining count), and states that panel images and Fast Pass state are never returned. Missing are explicit read/side-effect confirmation and any rate-limit or auth context, which the verb "Get" only implies.

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?

Front-loaded with the verb+resource, then return fields, then input routing, then pagination caveat, then error and exclusion notes. Sentences are long and dense, but none are filler; a slightly tighter split would improve scanning without losing information.

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 two-parameter read tool with no output schema and no annotations, the description covers return shape, pagination semantics, error behavior, and deliberate omissions. An agent has everything needed to call it and to interpret the response correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description earns extra: it explains that page is fixed at ten episodes per window and how the window relates to has_next_page, and it tells where title_no originates. That is meaningfully more than the schema's per-property text.

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?

States a specific verb and resource ("Get a WEBTOON series with a page of its episode list") and enumerates exactly what is returned: title, genre, authors, summary, cover, view/subscribe counters, release-day line, and the episode window fields. That scope is clearly narrower and different from the listing siblings (genre/originals/rankings/search), so an agent can pick it without opening the schema.

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?

Gives concrete input routing: "Take title_no from any listing card," which tells the agent to call a listing endpoint first. It does not spell out an explicit when-not or name an alternative by name, but the single-series-detail vs. listing distinction is unambiguous from the framing.

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