Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

webtoon_rankings

Fetch a WEBTOON chart tab (trending, popular, originals, or canvas) to get 30 ranked series with rank, title, genre, thumbnail, URL, and site counter.

Instructions

List one WEBTOON chart. Returns one fixed WEBTOON (webtoons.com) chart: thirty ranked series with rank position, title number, title, genre, thumbnail, canonical URL and the site's own counter. Four tabs exist; the chart size is fixed and there is no paging.

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_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoRanking tab, defaults to trending

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/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 behavioral burden and does well: it discloses the exact return shape (rank, title number, title, genre, thumbnail, URL, site counter), states the chart size is fixed at thirty, and explicitly says there is no paging. It omits any mention of rate limits, auth, or failure behavior, which keeps it short of a 5.

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 verb and resource, then the return contract, then the sizing/paging constraint. Slight redundancy between 'one WEBTOON chart' and 'one fixed WEBTOON chart' is the only waste.

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?

For a single-parameter tool with no output schema, the description compensates well by enumerating return fields and declaring the fixed chart size and absence of paging. What remains missing is any differentiation of what each tab surfaces, which would help an agent choose tab values.

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 enum already documents the four tab values with a default of trending. The description's note that 'four tabs exist' corroborates the enum but adds no new meaning about what each tab contains beyond what the schema supplies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('List one WEBTOON chart') and immediately narrows the scope to a single fixed chart of thirty ranked series. It distinguishes itself from broader sibling tools like webtoon_search or webtoon_series by emphasizing the fixed, non-paged chart structure, though it never names a sibling explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the tool for ranked-chart retrieval, and the mention of four tabs hints that other tools cover genre/originals browsing. However, there is no explicit when-to-use or when-not-to-use guidance, and no routing to alternatives like webtoon_genres or webtoon_originals.

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