Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_genres

List DramaBox genres as IDs and names so you can select a genre ID for browsing DramaBox titles.

Instructions

List DramaBox genres. Returns the genres DramaBox's browse accepts (Romance, Werewolves, Revenge, Billionaire, ...) as ids and names, read live from DramaBox. Pass a genre id to dramabox-browse. 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?

No annotations are provided, so the description carries the burden, and it does disclose that data is read live from DramaBox, contains only public catalog metadata, and returns no playable video — a useful negative guarantee. It stops short of noting stability/caching or that the genre set varies by locale, which the language parameter implies.

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?

Four short sentences, front-loaded with the purpose before the examples and the hand-off to dramabox_browse. Nothing is padded, though the final sentence about playable video slightly repeats the read-only framing already implied by "catalog metadata".

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?

With no output schema, the description does the work of stating that genres come back as ids plus names, which is exactly what an agent needs to chain into dramabox_browse. It is a zero-required-parameter listing tool, so little else is essential; the locale-dependence gap is the only real omission.

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% and the single language parameter already documents its allowed locales and that each locale has its own title library. The description adds nothing about the parameter, so this sits at the baseline for a fully documented schema.

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?

States a specific verb and resource ("List DramaBox genres") and immediately clarifies what that means concretely by naming example genres (Romance, Werewolves, Revenge, Billionaire) and the returned shape (ids and names). An agent can distinguish this from dramabox_browse without opening either 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?

Explicitly states the downstream use: "Pass a genre id to dramabox-browse." That is real routing guidance tied to a named sibling. It does not, however, disambiguate against the other taxonomy-ish siblings (dramabox_categories, dramabox_tag, dramabox_channels), so the agent must infer which taxonomy to fetch.

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