Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reelshort_search

Search ReelShort short dramas by title or keyword to retrieve paginated public catalog details such as IDs, descriptions, covers, episode counts, tags, plays, and favorites.

Instructions

Search ReelShort short dramas by title. Searches ReelShort (reelshort.com) short dramas by keyword and returns 12 titles per page: id, title, description, cover, link, episode count, tags, plays and favorites, with the page, page count and an approximate total. The search is fuzzy and the total varies between calls. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 200; defaults to 1. Each page holds 12 titles
keywordsYesTitle text to search for, up to 100 characters
languageNoSite locale, one of: en, es, pt, fr, de, it, ja, ko, th, id, tr, ar, ru, pl, ro, cs, bg, vi, zh-TW; defaults to en. Titles and tags are translated

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 full load and does it well: 12 results per page, fuzzy matching, an unstable approximate total, and an explicit 'no playable video is returned' scope limit. It stops short of stating auth or rate-limit behavior, which for an unannotated read tool leaves a small gap.

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 purpose, then result shape, then caveats — a sensible ordering with no filler. The middle sentence is dense with field enumerations, but each item is load-bearing given the absence of an output schema.

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, so the description must describe the return payload and does: field list, page/page count/total, pagination size, plus volatility and scope caveats. An agent has everything needed to call and interpret the result.

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 baseline is 3. The description reinforces the keywords semantics and the 12-per-page behavior of page, but adds nothing about the language enum or its 'titles and tags are translated' behavior that the schema already documents.

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 (search) and resource (ReelShort short dramas) plus the search field (by title), which is enough to separate it from reelshort_tag_search and reelshort_tag_books in a very crowded ReelShort sibling set.

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?

The 'by title' scoping implicitly routes the agent away from the tag-based siblings and toward this tool when it has a name fragment. It doesn't explicitly name the alternatives (reelshort_movie for known IDs, reelshort_tag_search for tag browsing), so it falls short of a 5.

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