Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_channels

Lists DramaBox theater channels with their IDs and names—Popular, New, Rankings, Categories, Anime, Live-Action, VIP, and Original+—for selecting catalog channels.

Instructions

List DramaBox theater channels. Returns the 8 DramaBox app theater channels as ids and names: Popular, New, Rankings, Categories, Anime, Live-Action, VIP and Original+. The channel value for dramabox-theater is the lowercase name (popular, new, rankings, categories, anime, live-action, vip, original). Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does add real behavioral context: it declares the read scope ("Only public catalog metadata is read") and rules out media ("no playable video is returned"). Side-effect and safety profile are covered; pagination/rate behavior is not, though with a fixed set of 8 items that is minor.

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?

Three sentences, front-loaded with the purpose, then the payload, then the scope caveat. The dual listing of display names and slugs is not waste — the slug form cannot be mechanically derived from "Original+", so both are needed.

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?

There is no output schema, so the description must describe returns — and it does, naming the 8 channels, the id/name pairing, and the slug transformation, plus the negative constraint about video. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so baseline is 4. The description goes further by specifying the shape of the returned channel values and the lowercase slug convention (including the non-obvious 'original' for 'Original+'), which is the key detail an agent needs for follow-up calls.

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+resource ("List DramaBox theater channels") and immediately enumerates the exact contents (8 channels). An agent knows precisely what comes back without opening anything else.

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?

The sentence "The channel value for dramabox-theater is the lowercase name..." implicitly routes the agent: call this first to obtain valid channel values for the sibling dramabox_theater. However, it never explicitly contrasts with dramabox_genres, dramabox_categories, or dramabox_home, so an agent must infer which taxonomy tool it needs.

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