Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_trending

Retrieve DramaBox search landing feeds—hot, trending, new-release lists, ranking tabs, and preset keyword—for app discovery and ranking lookups.

Instructions

Get DramaBox's search landing feeds. Returns the DramaBox Android app API's search landing page: the hot, trending and new-release title lists, the ranking tabs (pass a tab's type to dramabox-rank as rank_type) and the app's preset search keyword. Takes no parameters. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so: it discloses that only public catalog metadata is read and that no playable video is returned, setting correct expectations about a read-only, non-media response. It doesn't mention rate limits, caching, or region/locale behavior, which keeps it out of the top band.

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 the one-line purpose before the detail sentence, and every clause adds concrete content (returned lists, cross-tool routing, read-only scope). The second sentence is long and dense, but it is doing real work rather than 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?

No output schema and no annotations exist, so the description must convey what comes back and what the safety profile is; it lists the returned content groups and declares the read-only, metadata-only nature. An agent can call it correctly with no parameters and knows what to expect. Only the exact field shapes remain unspecified, which is acceptable without an output schema.

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?

The tool has zero parameters and the description states 'Takes no parameters,' matching the empty schema. Nothing further is required, so the baseline of 4 applies with no gap to penalize.

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?

States a specific verb and resource ('Get DramaBox's search landing feeds') and then enumerates the payload: hot, trending, new-release lists, ranking tabs, and the preset search keyword. This disambiguates from the name alone, which could suggest a single trending list rather than the whole landing page. It stops short of naming the closest sibling (dramabox_home, dramabox_browse) as a contrast.

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?

Provides an explicit cross-tool routing hint: a tab's type should be passed to dramabox-rank as rank_type, which tells an agent what to do after this call. It also clarifies usage boundaries by noting it takes no parameters. No explicit 'when not to use this vs. X' exclusion is given, but the follow-on route is concrete.

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