Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

dramabox_performer

Read-only

Get one DramaBox performer and one page of the titles they appear in: name, gender, avatar, video count, follow flag, and each title's id, title, description, cover, link, episode count, tags with tag ids, library flag and listing times. Get performer ids from dramabox_search or dramabox_suggest's people results. Only public catalog metadata is returned, never playable video.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "performer_id": "<performer_id>"
    },
    "name": "dramabox_performer"
  }
}

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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds a useful scope constraint: only public catalog metadata is returned, never playable video. It also describes the response shape at a high level, though it does not discuss pagination behavior beyond the schema.

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?

Two front-loaded sentences with no filler. The long field enumeration earns its place by clarifying the response contents, and the final constraint sentence adds a meaningful boundary.

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?

Output schema exists and the description still meaningfully names the key returned fields and data boundary. An agent has enough to invoke it correctly, though it could mention pagination defaults or result limits more explicitly, even though the schema covers those parameters.

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 page, limit, and performer_id are already documented in the schema. The description links performer_id back to search/suggest results, which adds some context, but it does not add syntax or constraints beyond the schema's own descriptions.

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?

Starts with a specific verb and resource: 'Get one DramaBox performer and one page of the titles they appear in', then enumerates the returned performer fields and title fields. This clearly distinguishes it from sibling search/suggest/catalog tools by making it a performer-detail-plus-filmography lookup.

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 tells the agent where to get performer ids: from dramabox_search or dramabox_suggest's people results. It does not explicitly state when to choose this over other detail tools such as dramabox_drama, but the prerequisite guidance is clear and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources