Crawlora MCP

webtoon_series

Read-only

Get one WEBTOON series and return its title, genre, authors, summary, cover, canonical URL, RSS feed, WEBTOON's own view and subscribe counters, the release-day line, and a page of its episode list (episode number, title, release date, thumbnail, viewer URL, UP badge). Get title_no from webtoon_genre, webtoon_originals or webtoon_rankings. WEBTOON publishes no total episode count, so has_next_page only reports that the page window was full; an unknown title number is a 404. Catalog metadata only, never panel images.

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

Name	Required	Description	Default
`page`	No	1-based episode page, default 1. Ten episodes per page; a page past the end clamps to the last page. Page 0 is rejected.
`title_no`	Yes	Required WEBTOON title number, e.g. 7830. Take it from a card's title_no in any listing endpoint.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description goes further by disclosing that WEBTOON publishes no total episode count so has_next_page only means the page window was full, that an unknown title_no yields a 404, and that the tool returns no panel images. These are non-obvious failure-mode and scope details an agent could not infer from structured fields.

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 purpose, then ID provenance, then pagination caveat and scope boundary — each sentence carries real information. The long enumeration of returned fields is partly redundant given an output schema exists, which is the only meaningful waste.

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-only, single-resource lookup with an output schema, the description covers everything an agent needs: identity of the resource, where the required ID comes from, pagination limits, error behavior, and content scope. Nothing material is missing.

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 the schema already documents the 1-based page, ten-per-page size, end-clamping behavior, and that title_no comes from a listing card. The description adds little beyond restating pagination behavior, so the baseline 3 is appropriate for a schema that carries the parameter semantics.

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+resource ('Get one WEBTOON series') and enumerates the returned fields, immediately distinguishing it from the listing siblings (webtoon_genre, webtoon_originals, webtoon_rankings). An agent can tell this is the single-series detail lookup 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?

Explicitly routes the agent to webtoon_genre, webtoon_originals, or webtoon_rankings to obtain title_no, and scopes usage with 'Catalog metadata only, never panel images.' No explicit when-not-to-use case is stated, but the ID-provenance guidance covers the main selection risk.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?