Crawlora MCP

dramabox_more

Read-only

Get a whole DramaBox curated shelf (trending, must-sees or hidden-gems), 18 short dramas per page, with each title's id, title, description, cover, link, episode count, tags, genres and displayed views, plus the page count. Only public catalog metadata is returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "position": "<position>"
    },
    "name": "dramabox_more"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number, 1 to 1000; defaults to 1. Each page holds 18 titles
`language`	No	Site 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.
`position`	Yes	Curated shelf: trending, must-sees or hidden-gems. Documented values: trending, must-sees, hidden-gems.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds useful scope context ('Only public catalog metadata is returned') and the per-page item count, but says nothing about pagination limits beyond the schema, rate limits, or locale-specific behavior.

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 front-loaded sentence that leads with the action and resource. It is somewhat list-heavy in enumerating eight returned fields, which is redundant given the output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is low-complexity, all parameters are documented, an output schema exists, and annotations carry the safety profile — so the description is mostly sufficient. The one real gap is sibling disambiguation, which matters because four dramabox tools share this space.

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 every parameter (page, language, position) is already documented in the schema, including valid values. The description restates the shelf names and page size but adds no new semantics beyond what structured fields provide — baseline 3 is appropriate.

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: 'Get a whole DramaBox curated shelf' with the three shelf kinds enumerated, and describes the returned fields. It does not name or contrast the sibling tools (dramabox_browse, dramabox_home, dramabox_genres), so an agent must infer which shelf-like tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is provided. It doesn't say how this differs from dramabox_browse or dramabox_home, nor which shelf to prefer for a given intent, leaving selection among four dramabox tools to guesswork.

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

All Crawlora MCP tools Inspect

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

Need Help?