Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_drama

Fetch a DramaBox short drama's title, description, cover, languages, tags, genres, view counts, follows, episode list, and related titles using a title ID or dramabox.com URL.

Instructions

Get a DramaBox short drama and its episodes. Returns one DramaBox short drama: title, description, cover, link, language, episode count, lifetime views, follows, tags, genres, listing times, the languages it is available in, the episode list with each episode's number, id, duration, free flag and thumbnail, and related titles. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
idYesTitle id (digits) from any DramaBox list, or a dramabox.com drama URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/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 well: it declares the read-only scope ("Only public catalog metadata is read") and explicitly rules out playable video, preventing a false expectation. It does not cover error behavior or whether unpublished/region-locked titles return empty, so it falls 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?

The purpose sentence is front-loaded and the field enumeration earns its length because there is no output schema. The middle sentence is a dense comma-run of return fields, slightly heavy but not redundant.

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 exists, so enumerating the returned fields (title, episodes with duration/free flag/thumbnail, related titles, etc.) is genuinely necessary and it is done thoroughly, alongside the read-only/no-video caveat. The only gap is the absence of sibling routing guidance.

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% and the single id parameter already documents both accepted forms (digits from any DramaBox list, or a dramabox.com URL). The description adds nothing about the id beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ("Get a DramaBox short drama and its episodes") and immediately scopes it to a single item, which separates it from the list-oriented siblings (dramabox_search, dramabox_browse, dramabox_trending). An agent can tell this is the detail/lookup tool without opening the schema.

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 only implied: taking an id or a dramabox.com URL suggests it is the follow-up to a list/search call, but the description never names which sibling to call first or when to prefer another tool. No exclusions or preconditions are stated.

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