Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

dramabox_browse

Read-only

Browse DramaBox short dramas, 12 per page, optionally within one genre (get genre ids from dramabox_genres), and return each title's id, title, description, cover, link, episode count, tags, genres, rating and displayed views, with page and total pages. Only public catalog metadata is returned.

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_browse"
  }
}

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. Documented values: en, ko, zhHans, zh, es, ja, de, in, th, tl, pt, fr, ar, it.

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.8/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 context on top: fixed 12-per-page pagination, the exact result fields returned, and the scope-limiting note that "Only public catalog metadata is returned" — useful for knowing no paywalled/episode content arrives.

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?

A single dense sentence that front-loads the action, the page granularity, and the optional filter, then enumerates return fields. It is slightly run-on and the return-field enumeration duplicates the output schema, but nothing is wasted or buried.

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?

An output schema exists, so the description need not document return structure, yet it still names the key fields and clarifies that pagination totals are included. Combined with complete schema coverage of all three optional parameters and the read-only annotations, an agent has everything required to call it 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 description coverage is 100%, so page, genre_id, and language are already fully documented in the schema, including the page cap and the locale enumeration. The description only echoes the page size and the genre-id source; it adds nothing about the language parameter or the per-locale library behavior beyond what the schema states.

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 page size and the genre-scoping option, so an agent knows exactly what it gets. It points at dramabox_genres for the genre-id dependency but does not distinguish itself from other catalog siblings such as dramabox_home or dramabox_more.

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 parenthetical "get genre ids from dramabox_genres" gives a useful ordering hint for the optional filter, implying a two-step workflow. However, there is no statement of when this tool is preferred over dramabox_home, dramabox_more, or a search-style call, so the selection guidance is implicit rather than 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