Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reelshort_movie

Fetch a ReelShort short drama's public metadata and full episode list by title ID or URL, including tags, cast, release times, and episode access details.

Instructions

Get a ReelShort short drama and its episodes. Returns one ReelShort short drama: title, description, cover, link, language, episode count, plays, favorites, badge, dubbed and AI-generated flags, release times, tags with their kind (genre, style, mood, trope and more), cast with IMDb links, and the full episode list with each episode's id, number, link, likes, release time and whether it is free. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
idYesTitle id (24 hex characters) from reelshort-home, reelshort-shelf or reelshort-search, or a reelshort.com movie or episode URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the load and does well: it discloses that only public catalog metadata is read and explicitly that 'no playable video is returned,' which prevents a false expectation about content access. It doesn't mention auth or rate limits, but the return-vs-not-returned framing is genuinely useful.

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 core action in the first sentence, then a structured enumeration of returned fields. The field list is long but every item earns its place by describing the return payload, which is necessary since there is no 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?

With no output schema and no annotations, the description must explain the return shape, and it does so comprehensively down to per-episode fields and flag meanings. An agent knows exactly what it gets back and that no video is included.

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 id parameter is fully documented in the schema (including the 24-hex-char format and accepted sources). The description adds nothing beyond what the schema already provides, so baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Get a ReelShort short drama and its episodes.' An agent can tell this is the detail lookup distinct from search/shelf/home tools. It doesn't explicitly name the siblings it differs from, so a 4 rather than a 5.

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?

Usage is implied — retrieve a single drama by id — but there is no explicit 'use this when you have an id from search/shelf/home, not for browsing' guidance in the description. The only routing hint lives in the schema's id description, not the tool description itself.

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