Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_theater

Fetches a DramaBox theater channel feed with shelves, banner posters, search hot words, and public title metadata such as episode counts, tags, and play counts.

Instructions

Get a DramaBox theater channel feed. Returns one page of a DramaBox app theater channel: the channel, its titled shelves (each with styles and 10 to 20 titles), poster banners and search hot words. Each title carries its id, title, description, cover, website link, episode count, tags with tag ids, protagonist, play count, library flag and listing times. Channel values are the lowercase names from dramabox-channels. An empty feed is a valid answer. Only public catalog metadata and poster images are read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 1000; defaults to 1
limitNoTitles per paged block, 1 to 20; defaults to 10
channelYesTheater channel: popular, new, rankings, categories, anime, live-action, vip or original

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 does real work: it states 'only public catalog metadata and poster images are read; no playable video is returned,' clarifying the read-only, non-media nature. It also flags an edge case ('An empty feed is a valid answer'), though it doesn't touch permissions or rate limits.

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 purpose, then details return contents and edge cases. Every sentence carries information (field list, empty-feed validity, read-only scope); slightly dense but not padded.

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?

There is no output schema, but the description compensates by enumerating the returned structure (channel, shelves, banners, hot words, per-title fields). Combined with the read-only and empty-feed notes, an agent has what it needs to call and interpret it.

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?

Schema coverage is 100%, so baseline would be 3, but the description adds meaning beyond the schema by stating the channel enum values derive from the dramabox-channels tool. Page/limit semantics are left entirely to their schema descriptions.

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?

Opens with a specific verb+resource: 'Get a DramaBox theater channel feed,' and scopes it to 'one page of a DramaBox app theater channel.' It clearly reads a channel feed rather than a browse/home/rank list, though it never names a sibling tool to explicitly differentiate itself.

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?

Usage is only implied: 'Channel values are the lowercase names from dramabox-channels' tells the agent where to source channel names, which is useful routing. But there is no explicit when-to-use-this vs dramabox_browse/dramabox_home/dramabox_channels guidance or exclusion of alternatives.

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