Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

reelshort_search

Read-only

Search ReelShort short dramas by keyword and return 12 titles per page with each title's id, title, description, cover, link, episode count, tags, plays and favorites, plus the page count. The search is fuzzy and the total is approximate. Use this to find a title's id for reelshort_movie. Only public catalog metadata is returned.

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": {
      "keywords": "<keywords>"
    },
    "name": "reelshort_search"
  }
}

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. Documented values: en, es, pt, fr, de, it, ja, ko, th, id, tr, ar, ru, pl, ro, cs, bg, vi, zh-TW.

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 cover read-only/open-world, but the description adds genuine behavioral context: fuzzy matching, approximate totals, 12 titles per page, and that only public catalog metadata is returned. That materially affects how an agent should interpret results, though it says nothing about rate limits or pagination limits 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and result shape, then the return fields, then the usage pointer. Three sentences with little waste, though the full field enumeration is somewhat verbose for what the output schema likely already conveys.

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?

An output schema exists, yet the description still frames the result set (12 per page, approximate totals, public metadata only) and the downstream use. Nothing an agent needs to call this correctly is missing.

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 keywords, page, and language are already documented. The description restates the 12-per-page size and the fuzziness of the match, which marginally adds interpretation value but no new parameter syntax. Baseline 3 is appropriate.

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 by keyword) and immediately describes the paginated result shape. It names reelshort_movie as the sibling this tool feeds into, so the agent can distinguish its role in the ReelShort toolset.

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?

"Use this to find a title's id for reelshort_movie" gives a concrete when-to-use and points to the follow-on sibling. It doesn't explicitly exclude the other ReelShort siblings (reelshort_home, reelshort_shelf, reelshort_fandom_*), so the routing is clear but not fully closed.

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