Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

webtoon_search

Search WEBTOON series by keyword and get grouped ORIGINALS and CANVAS results with titles, creators, genre, URL, thumbnail, views, badges, adult flag, and type; use title_no for episode data.

Instructions

Search WEBTOON series by keyword. Returns one page of WEBTOON (webtoons.com) search results, grouped into the page's own ORIGINALS and CANVAS sections. Each card carries its title number, title, authors, genre path segment, absolute URL, thumbnail, WEBTOON's own view counter, UP badge, adult flag and normalized webtoon_type; pass a card's title_no to webtoon-series for episode metadata. scope selects the site's own tab: all (the default) is a combined preview of at most 12 cards per section and cannot be paged, while originals and canvas serve up to 30 cards per page and return an empty sections list for a page past the end. A keyword that matches nothing is a valid 200 with no sections. Search cards carry no genre label, so genre is the hyphenated path segment from the card's own href (map it through webtoon-genres for webtoon-genre) and is empty for canvas cards.

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": {
      "keyword": "<keyword>"
    },
    "name": "webtoon_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-based results page; page above 1 requires scope=originals or scope=canvas
`scope`	No	Search scope: the site's own ALL, ORIGINALS or CANVAS tab
`keyword`	Yes	Keyword to search series titles and creators for

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.7/5.0

Behavior5/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: it discloses per-scope page caps (12 cards per section for all, 30 for originals/canvas), that a page past the end returns an empty sections list, and that a non-matching keyword is a valid 200 with no sections. It also enumerates every returned card field and flags that canvas cards have an empty genre segment.

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 progressively narrower detail about paging, empty results, and card shape — a sensible ordering. It runs long as a single dense paragraph with several embedded clauses, so a bulleted structure would improve scanability, but every sentence carries informational weight.

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?

There is no output schema, yet the description fully specifies the returned card fields (title_no, title, authors, genre segment, URL, thumbnail, view count, UP badge, adult flag, webtoon_type) plus the envelope behavior (sections, empty cases). That is everything an agent needs to call it and reason about the response.

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

Parameters5/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 adds real semantics the schema does not: the concrete card counts per scope value, the paging restriction tying page>1 to originals/canvas, and the empty-result contract. It also clarifies that keyword matches titles and creators, not just titles.

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 ("Search WEBTOON series by keyword") and immediately characterizes the result set as one page of webtoons.com search results split into ORIGINALS and CANVAS. It names the sibling tools it hands off to (webtoon-series for episode metadata, webtoon-genres for genre mapping), so the agent can place it in the tool graph without opening other schemas.

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?

Explains what each scope value does and forbids paging under scope=all ("cannot be paged"), and points to webtoon-series for episode metadata and webtoon-genres for genre normalization. It lacks an explicit statement of when to prefer this over webtoon_originals or webtoon_rankings, which is the remaining gap.

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

Deploy Server