Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_performer

Retrieve a DramaBox performer's profile and paginated title credits using a performer ID from search or suggest results, returning public catalog metadata such as name, avatar, video count, and titles.

Instructions

Get a DramaBox performer and their titles. Returns one DramaBox performer from the Android app API: name, gender, avatar, video count, follow flag, and one page of the titles they appear in (each with id, title, description, cover, website link, episode count, tags with their tag ids, protagonist, library flag and listing times). Get performer ids from dramabox-search or dramabox-suggest's people results. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 1000; defaults to 1
limitNoPage size, 1 to 20; defaults to 10
performer_idYesPerformer id from dramabox-search or dramabox-suggest's people results

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 provided, the description carries the burden and does well: it discloses that only public catalog metadata is read, that no playable video is returned, and that the title list is limited to a single page. Missing are any notes on error behavior for an invalid performer id or on rate/permission constraints, which keeps it from a 5.

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 action and then the payload; every sentence is functional. The long parenthetical listing each title field is dense but earns its place given there is no output schema, though it could be trimmed slightly.

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?

Without an output schema, the description compensates by enumerating the returned performer and title fields, and it explains the pagination ceiling. What it omits — behavior when the id is unknown or the page is out of range — is minor for a read-only lookup tool.

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%, so the baseline is 3. The description does echo the two behaviors that matter — one paginated slice of titles and where performer_id must come from — which aligns with the schema's page/limit/performer_id descriptions but adds little beyond them.

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 ('Get a DramaBox performer and their titles') and immediately enumerates what comes back: name, gender, avatar, video count, follow flag, plus a page of titles with their fields. This is specific enough to distinguish it from catalog-wide siblings like dramabox_drama or dramabox_browse.

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 routes the agent to the prerequisite lookup source: 'Get performer ids from dramabox-search or dramabox-suggest's people results.' That is a clear context-setting instruction. It stops short of stating when NOT to use it (e.g., when you only want the dramas themselves, use dramabox_drama), so it isn't a full when/when-not pair.

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