Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_rank

Fetch a DramaBox ranking list by tab type—Most Trending, Top Searched, or New Releases—to get 20 ranked titles with public catalog metadata for research.

Instructions

Get a DramaBox ranking list. Returns one DramaBox ranking list from the DramaBox Android app API: the available tabs (Most Trending, Top Searched, New Releases) and 20 ranked titles, each with its id, title, description, cover, website link, episode count, tags, protagonist, rank position, hot metric, library flag and listing times. Pass a tab's type as rank_type to read that tab. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
rank_typeNoRanking tab: 1 (Most Trending), 2 (Top Searched), 3 (New Releases); omit for the default tab

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses that only public catalog metadata is read and that no playable video is returned. It also describes the return contents, though it does not cover auth or rate-limit behavior.

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 purpose and return contents are front-loaded and no sentence is irrelevant. There is minor repetition ('Get a DramaBox ranking list' followed by 'Returns one DramaBox ranking list') and a long field list, but it remains efficient for the amount of return detail conveyed.

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, so the description must explain return values, and it does: available tabs, 20 ranked titles, and the metadata fields. For a one-optional-parameter read tool with no annotations, this is complete enough to call correctly.

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 description coverage is 100%, so the enum mapping and default-tab behavior are already fully documented in the schema. The description repeats that mapping rather than adding new parameter semantics, making the baseline 3 appropriate.

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 gives a specific verb and resource ('Get a DramaBox ranking list') and states the exact return scope: tabs plus 20 ranked titles with catalog metadata. It is clear, but it does not explicitly distinguish this ranking list from sibling tools such as dramabox_trending or dramabox_home.

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?

It explains how to use the optional parameter ('Pass a tab's type as rank_type to read that tab'), which implies the tool's usage. However, it does not say when to choose this ranking tool over alternatives like dramabox_trending, dramabox_home, or dramabox_search.

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