Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reelshort_new_releases

Fetch ReelShort's curated New Release list as JSON, returning up to 18 titles with IDs, covers, links, episode counts, plays and favorites for catalogue research.

Instructions

List ReelShort's curated New Release titles. Returns ReelShort's (reelshort.com) curated "New Release" list from its website's signed JSON API: up to 18 titles with id, name, description, cover, reelshort.com link, episode count, plays, favorites and the first paid episode. book_id is a 24-character title id required by ReelShort's own API; on 2026-10-26 four different values, including an unknown id, returned the same list, so it is not known to change the result. Only public catalogue data is read and no playable media is returned.

Input Schema

NameRequiredDescriptionDefault
book_idYesA 24-character title id, from reelshort-movie, reelshort-shelf or reelshort-home; required by ReelShort but not observed to change the result
languageNoSite language, 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so: it discloses the result cap (18 titles), the exact returned fields, that only public catalogue data is read, that no playable media is returned, and it documents an observed book_id quirk with a date and test evidence. That is far richer than a restatement of the name.

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?

Four sentences, no padding, and it is front-loaded with what the tool returns before moving to provenance, field list and caveats. Every clause conveys information an agent would otherwise have to guess.

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 and no annotations, so the description must supply the return shape and safety profile itself — and it does, enumerating the returned fields and confirming no media is returned and only public data is read. Nothing needed to call it correctly is missing.

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%, so the baseline is 3; the description adds genuinely new meaning by reporting that four different book_id values including an unknown id returned the same list, which materially changes how an agent fills that required field. The language parameter is left to the enum in the schema, so it is not a full 5.

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 curated New Release titles, and names the source (reelshort.com's signed JSON API) plus the exact payload (up to 18 titles with named fields). It is unambiguously distinct from siblings like reelshort_home, reelshort_shelf and reelshort_search.

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?

Gives useful operational context: book_id is required by the upstream API but was empirically observed not to affect the result, which tells an agent it needn't hunt for a valid id. However, it never states when to prefer this over reelshort_home/reelshort_shelf/reelshort_search, so no explicit exclusions or alternatives are offered.

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