Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_search

Search DramaBox titles and performers by keyword, returning paginated mixed catalog results with book and performer metadata for discovery.

Instructions

Search DramaBox titles and performers. Searches the DramaBox Android app API and returns one page of mixed results: book rows (id, title, description, cover, website link, tags, protagonist) and performer rows (id, name, avatar, series count), plus an is_more flag for the next page. The keyword is trimmed and truncated to 80 characters like the app; sort selects one of the app's result orderings. Performer ids can be passed to dramabox-performer. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based result page
sortNoUpstream result ordering mode; omit for the app default
limitNoResults per page
keywordYesSearch text, trimmed and truncated to 80 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.7/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 well: it declares the read-only surface ('Only public catalog metadata is read; no playable video is returned'), explains pagination via the is_more flag, and notes keyword trimming/truncation to 80 characters like the app. Missing only auth/rate-limit or empty-result behavior.

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?

Purpose is front-loaded in the first sentence, followed by return shape, then parameter notes. The row-field enumeration is dense but earns its place given there is no output schema; little waste overall.

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 4-param search tool with no annotations and no output schema, the description supplies the return structure, pagination signal, and data-safety scope, which is close to sufficient. Minor gaps remain around no-results behavior and default page/limit values.

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%, so keyword, page, sort, and limit are already documented. The description largely restates the schema (keyword truncation, sort as app ordering modes) rather than adding new semantics, so baseline 3 applies.

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?

Opening sentence gives a specific verb and resource ('Search DramaBox titles and performers') and the mixed book/performer row shape distinguishes it from browse/category siblings. It does not explicitly contrast itself with dramabox_suggest or dramabox_browse, so sibling routing is left partial.

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 implied by the keyword-driven search framing, and the note 'Performer ids can be passed to dramabox-performer' gives a useful downstream workflow cue. However, there is no explicit statement of when to use this versus alternatives such as dramabox_suggest (autocomplete) or dramabox_browse/category tools.

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