Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_home

Lists featured short dramas and curated home-page shelves—Trending, Must-sees, and Hidden gems—with title IDs, covers, genres, episode counts, tags, and view counts by locale.

Instructions

List DramaBox's featured titles and shelves. Returns DramaBox's (dramabox.com) home page: the featured short dramas and the three curated shelves (Trending, Must-sees, Hidden gems), each title with its id, title, description, cover, DramaBox link, episode count, tags, genres and the view count as the site prints it. Use dramabox-more for a whole shelf. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
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

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 full burden and does so well: it declares read-only scope ('Only public catalog metadata is read') and explicitly rules out playable video. It omits pagination behavior and how the three shelves are ordered or truncated, which is the remaining behavioral gap.

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?

Front-loaded with the core action, then the return payload, then the sibling pointer and the scope disclaimer. The field enumeration is long but earns its place because no output schema exists; it is slightly dense to read in one pass.

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?

The tool has no output schema and no annotations, so the description must cover both, and it does: it names the returned fields per title and the safety profile. Missing only pagination/shelf-truncation details, which matters little for a fixed home-page fetch.

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% and the single 'language' parameter is fully documented in-schema, including the enum, the Indonesian disambiguation, and the default. The description adds nothing about the locale parameter (e.g. that switching locale changes which titles appear), so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('List DramaBox's featured titles and shelves') and then enumerates exactly what the home page contains, including the three named shelves. An agent can tell it apart from dramabox_more, dramabox_trending and dramabox_browse without opening any schema.

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?

It explicitly routes to 'dramabox-more for a whole shelf', giving the agent a concrete alternative and the condition that selects it. It stops short of a fuller when/when-not statement (e.g. versus dramabox_trending or dramabox_rank), so it is clear context rather than complete routing guidance.

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