Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_browse

Browse DramaBox short dramas by genre and page through catalog metadata, including titles, covers, ratings, tags, and episode counts; use genre IDs from dramabox-genres.

Instructions

Browse DramaBox short dramas by genre. Returns one page of 12 DramaBox short dramas, optionally within one genre: id, title, description, cover, link, episode count, tags, genres, rating, update status and displayed views, with the page and total page count. Genre ids come from dramabox-genres. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 1000; defaults to 1. Each page holds 12 titles
genre_idNoGenre id from dramabox-genres; 0 or omitted browses all titles
languageNoSite locale, one of: en, ko, zhHans, zh, es, ja, de, in, th, tl, pt, fr, ar, it (in is Indonesian); defaults to en. Each locale has its own title library

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 well: it discloses pagination behavior (page of 12, plus page and total page count in the response), enumerates the returned metadata, and states "Only public catalog metadata is read; no playable video is returned" — a clear read-only safety statement. It omits auth/rate-limit or locale-library consequences, so not 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?

Three sentences, front-loaded with what the tool does and what it returns; the field enumeration is a bit list-like but each item helps an agent decide whether the response has the data it needs. Little waste, though the field list could have been condensed.

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?

No output schema and no annotations, yet the description covers return shape, pagination, filter source and read-only scope — everything needed to invoke and interpret the 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 coverage is 100%, so page, genre_id and language are already fully documented, and the description's "one page of 12" and "Genre ids come from dramabox-genres" largely restate the schema text. It adds only the framing that genre scoping is optional; the locale-per-library nuance is left entirely to the schema.

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 ("Browse DramaBox short dramas") plus the filtering axis (by genre) and the result granularity (one page of 12). It does not explicitly contrast with nearby siblings like dramabox_search, dramabox_trending or dramabox_category_books, so an agent must infer that this is the catalog-listing endpoint rather than a keyword search.

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?

"optionally within one genre" makes clear the genre filter is optional, and "Genre ids come from dramabox-genres" gives the prerequisite step before calling. No negative guidance or explicit alternative (e.g. use dramabox_search when you have a title keyword) is offered, keeping it below a 5.

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