Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora.mcp
OverviewDiscussionsAdmin

dramabox_category_books

Read-only

Browse DramaBox short dramas through the app's category filters: pass values from dramabox_categories as language, production, dub, genre, genre_2 and/or sort (all optional and combined with AND), plus page and limit, and get each title's id, title, description, cover, link, episode count, tags with their tag ids, library flag and listing times. Only public catalog metadata is returned, never playable video.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dramabox_category_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
dubNoDub-mode value from dramabox-categories' dub group: 1 (Dubbed), 0 (Subtitles Only). Documented values: 1, 0.
pageNoPage number, 1 to 1000; defaults to 1
sortNoSort value from dramabox-categories' sort group: 1 (Trending), 2 (Latest), 3 (Unwatched). Documented values: 1, 2, 3.
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). Documented values: 3, 1, 2.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral boundaries by stating that only public catalog metadata is returned and never playable video, which is useful context beyond the annotations.

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 definition is front-loaded with purpose and remains compact despite covering eight parameters and return fields. The second sentence is dense but every clause contributes useful information, with no obvious filler.

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?

Given the rich structured data available — full parameter descriptions, annotations, and an output schema — the description is complete enough. It adds the key workflow dependency on dramabox_categories, the AND-combination rule, and the no-playable-video boundary, so an agent has what it needs to invoke the tool correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description adds useful semantics beyond the schema by explaining that all filters are optional and combined with AND, and by directing the agent to source filter values from dramabox_categories. It does not need to repeat every parameter description because the schema already does so.

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 states a specific verb and resource: browse DramaBox short dramas through category filters. It clearly references dramabox_categories as the source of filter values, which helps separate this from generic search or browse tools, though it does not explicitly contrast with sibling tools like dramabox_search or dramabox_browse.

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?

The description gives practical usage instructions: pass values from dramabox_categories and note that all filters are optional and combined with AND. However, it does not explicitly state when to use this tool versus alternatives such as dramabox_search or dramabox_browse, so the usage guidance is implied rather than fully explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources