Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reelshort_home

Lists ReelShort home page drama shelves with titles, metadata, and paid-episode info; pass a shelf ID to reelshort-shelf for the full list.

Instructions

List ReelShort's home page shelves. Returns ReelShort's (reelshort.com) home page as ranked shelves of short dramas (New Release, TOP, Reel Original, Hidden Identity, and so on): shelf id and name, and for each title its id, title, description, cover, ReelShort link, episode count, tags, plays, favorites and the episode from which viewing is paid. Pass a shelf id to reelshort-shelf for the whole list. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
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.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does so well: it declares the data is read-only public catalog metadata, that no playable video is returned, and that shelves are ranked. The one gap is that it doesn't say how many shelves or titles come back per call, so size/limits remain unknown.

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?

Three sentences, front-loaded with purpose followed by return shape and then the sibling handoff. The middle sentence is a long field enumeration but every item earns its place given there is no output schema.

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?

No output schema exists, so enumerating the returned shelf and title fields is exactly the right compensatory move, and the read-only/no-video disclaimer is included. Only the absence of result-size expectations keeps it from a 5.

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% and the single language enum is fully documented with its default and the note that titles and tags are translated. The description adds nothing about the parameter, so the baseline 3 applies.

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 ('List ReelShort's home page shelves') and immediately disambiguates the unit of return: ranked shelves of short dramas with named examples (New Release, TOP, Reel Original). An agent can distinguish it from reelshort_shelf and reelshort_new_releases without opening any schema.

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?

It names the follow-up path explicitly ('Pass a shelf id to reelshort-shelf for the whole list'), which is genuine routing guidance to a sibling. It doesn't spell out when to prefer reelshort_new_releases or reelshort_search instead, so it falls short of a full when/when-not statement.

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