Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

webtoon_originals

Lists one day of WEBTOON's Originals release calendar, returning every updating series with title, genre, authors, thumbnail, canonical URL, and UP badge. Use the complete tab for finished series.

Instructions

List one day of WEBTOON's release calendar. Returns one day of WEBTOON's (webtoons.com) Originals release calendar: every series updating that day, with each series' title number, title, genre, authors, thumbnail, canonical URL, the site's own counter and the UP badge. The complete day is one document, so there is no paging. Use the complete tab for finished series.

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": {
      "day": "<day>"
    },
    "name": "webtoon_originals"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesRelease day tab
sortNoResult ordering

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does reasonably well: it discloses that the full day is returned as a single document with no paging, and it enumerates the returned fields including the site's own counter and the UP badge. It implies a read-only listing without stating it, and says nothing about rate limits or whether title numbers can be reused with a sibling series tool.

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?

The description leads with the action and scope, so the most important information is front-loaded. 'Returns one day of WEBTOON's Originals release calendar: every series updating that day' partially restates the opening sentence, and the trailing 'complete tab' note is slightly detached from the rest, but there is no padding.

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?

There is no output schema, so the description must describe return values and does so with a field list; there are no annotations, and the description compensates with the no-paging and single-document traits. For a two-parameter public read tool this is close to complete, with only auth/rate context and sort-direction meaning left unstated.

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 adds real meaning by explaining that the 'complete' value means finished series — something the schema's 'Release day tab' label does not convey. The 'sort' parameter (MANA/LIKEIT/UPDATE) gets no explanation in either place, which keeps this from a 5.

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 states a specific verb and resource: listing one day of WEBTOON's Originals release calendar, scoped to a single day rather than all series. It enumerates what a result entry contains (title number, title, genre, authors, thumbnail, URL, site counter, UP badge), which is more specific than the bare name. It stops short of naming which sibling tool to use instead (e.g. webtoon_series or webtoon_rankings), so differentiation is implied by scope rather than stated.

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?

The only explicit guidance is 'Use the complete tab for finished series', which disambiguates an otherwise cryptic enum value and is genuinely useful. There is no statement of when to prefer this tool over webtoon_series, webtoon_genre, or webtoon_rankings, and no mention of prerequisites or limits. Usage is therefore inferable from the resource name but not spelled out.

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