Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_category_books

Browse DramaBox short dramas by category using language, production type, dub mode, genre, and sort filters to retrieve paginated public catalog metadata.

Instructions

Browse DramaBox titles by category. Returns one page of 20 DramaBox short dramas from the app's category feed, optionally filtered by values from dramabox-categories: language, production type, dub mode, either genre row and sort order. Filters are ANDed; an omitted filter means all. Each title carries its id, title, description, cover, website link, episode count, tags with tag ids, protagonist, play count, library flag and listing times. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
dubNoDub-mode value from dramabox-categories' dub group: 1 (Dubbed), 0 (Subtitles Only)
pageNoPage number, 1 to 1000; defaults to 1
sortNoSort value from dramabox-categories' sort group: 1 (Trending), 2 (Latest), 3 (Unwatched)
genreNoGenre value from dramabox-categories' genre_1 group, e.g. 1357 (Romance) or 1361 (Strong Heroine)
limitNoTitles per page, 1 to 50; defaults to 20
genre_2NoGenre value from dramabox-categories' genre_2 group, e.g. 1392 (Second Chance) or 1359 (BL); multi-tag values such as 1324,1362 are one value
languageNoLanguage/origin value from dramabox-categories' language group, e.g. 美国 (Local) or 中国 (Chinese)
productionNoProduction-type value from dramabox-categories' production group: 3 (AI Drama), 1 (Live-Action), 2 (Anime)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.1/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 discloses read-only public catalog metadata, no playable video, page size of 20, and returned fields. It does not cover auth, permissions, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, filter behavior, return contents, and the no-video constraint in a compact paragraph. Every sentence adds scope or behavioral context without redundantly restating schema fields.

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?

For an eight-optional-parameter read-only catalog tool with no annotations or output schema, the description covers return scope, page size, filter semantics, and the key limitation that no playable video is returned. Pagination details are left to the schema, which is appropriate.

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 the schema already documents all eight parameters and their enums. The description adds useful filter semantics (ANDed, omitted means all, values from dramabox-categories), but not per-parameter syntax beyond 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 titles by category,' and clarifies it returns one page from the category feed. It does not explicitly contrast with sibling browse/genre/search tools, so sibling differentiation is implied 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains that filters are optional, ANDed, and that an omitted filter means all, and points to dramabox-categories for valid filter values. It lacks explicit when-to-use/when-not guidance or alternate sibling routing.

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