Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

webtoon_rankings

Read-only

List one fixed WEBTOON chart (trending, popular, originals or canvas) and return thirty ranked series with each one's 1-based rank, title_no, title, genre, thumbnail, canonical URL and WEBTOON's own counter. The chart size is fixed and there is no paging; use the ranking endpoints for what is charting and webtoon_genre for complete genre coverage.

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, one of: trending (default), popular, originals, canvas.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already carry readOnlyHint and openWorldHint, so safety is covered. The description adds genuine behavior beyond them: the chart size is fixed at thirty, there is no paging, and each call returns exactly one tab's chart. Enumerating the returned fields is somewhat redundant given an output schema exists.

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 what is returned, then the no-paging constraint, then the alternative routing, in two dense sentences. The full list of seven returned fields is slightly padded against an output schema that documents them.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A simple one-parameter read tool is nearly covered, but the description leaves open what the 'counter' measures (raw vs normalized) and whether order is strictly by rank. The return-field enumeration partly compensates for the output schema rather than adding new information.

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% and the enum is already in the schema, so the description need not repeat values. What it adds is the implication that the tab selects an entire dataset rather than filtering a larger pool — one chart per call, fixed size — which is a meaningful semantic point.

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?

Specific verb (List) plus resource (a fixed WEBTOON chart) and scope (one of four chart types), with the return shape spelled out as thirty ranked series with named fields. It distinguishes itself from webtoon_genre by naming that sibling as the route to complete genre coverage.

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?

States the use case ('what is charting'), notes there is no paging, and points to webtoon_genre when complete genre coverage is needed. It does not state when-not to use it or which sibling handles series lookup or search, so guidance is clear but not exhaustive.

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

All Crawlora MCP toolsInspect
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