Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dramabox_recommend

Retrieve one page of DramaBox's "You Might Like" recommendation feed, including titles, covers, tags, episode counts, and listing metadata for public catalog discovery.

Instructions

Get a page of DramaBox's recommendation feed. Returns one page of DramaBox's own "You Might Like" recommendation feed from the Android app API: the feed title and its titles, each with id, title, description, cover, website link, episode count, tags with their tag ids, protagonist, library flag and listing times. The upstream page size is fixed, so page is the only paging control. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 1000; defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.2/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 well: it discloses that the upstream page size is fixed so page is the only paging control, that only public catalog metadata is read, and that no playable video is returned. It does not mention rate limits or pagination termination, which keeps it short of 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?

The purpose and paging constraint are front-loaded in the first sentences, and the field enumeration is a single compact clause. Dense but nearly every element earns its place; the long field list is the only mildly padded part.

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?

No output schema exists, and the description compensates by enumerating the returned shape (feed title, titles with id, title, description, cover, link, episode count, tags, protagonist, library flag, listing times) plus the paging constraint. An agent has everything needed 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% and the schema already documents the page parameter and its 1-1000 range, so the baseline is 3. The description adds real value beyond the schema by explaining that upstream page size is fixed and page is the sole paging control.

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?

The description uses a specific verb+resource ("Get a page of DramaBox's recommendation feed") and pins down the exact upstream surface ("DramaBox's own 'You Might Like' feed from the Android app API"), which separates it cleanly from dramabox_trending, dramabox_browse, and dramabox_home.

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?

The "You Might Like" framing implies a discovery/recommendation use case, but the description never states when to choose this over the sibling feed tools (trending, browse, home) or any preconditions. Usage is inferable but not spelled out.

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