Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_more

Retrieve one page of a DramaBox curated shelf—trending, must-sees, or hidden-gems—with titles, tags, genres, episode counts, and links. Browse public catalog metadata without playable video.

Instructions

Get a whole DramaBox curated shelf. Returns one page of 18 titles from a DramaBox curated shelf (trending, must-sees or hidden-gems): id, title, description, cover, link, episode count, tags, genres and displayed views, with the page and total page count. 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 18 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
positionYesCurated shelf: trending, must-sees or hidden-gems

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does disclose important traits: it reads only public catalog metadata and returns no playable video. It also lists the returned fields and pagination behavior. It does not mention auth, rate limits, or error behavior, so it is strong but not complete.

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?

The description is front-loaded with the core purpose and then expands into returns and behavioral constraints. The long return-field list is justified because no output schema exists. There is no wasted phrasing.

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

Completeness4/5

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

For a three-parameter read-only browse tool with no annotations and no output schema, the description covers the return shape, pagination, and the no-video constraint. It leaves out the language/locale parameter and explicit sibling routing, but those are either documented in the schema or inferable from the tool set. It is complete enough to invoke 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 the schema already documents all three parameters including enums, defaults, and ranges. The description reinforces the shelf values and page size of 18, but it adds little beyond the schema and never mentions the language parameter. The baseline 3 is appropriate when the schema does most of the work.

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: getting a DramaBox curated shelf. It enumerates the three shelf values (trending, must-sees, hidden-gems), so the tool's purpose is clear. It does not explicitly distinguish itself from sibling tools such as dramabox_trending or dramabox_browse, so it falls short of a 5.

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 implies usage by saying it returns a curated shelf and by defining the position values, but it gives no explicit when-to-use or when-not-to-use guidance. It does not name alternatives such as dramabox_trending for a trending-only request. The usage context is therefore only implied.

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