Crawlora MCP

reelshort_movie

Read-only

Get one ReelShort short drama and return its title, description, cover, language, episode count, plays, favorites, tags (genre, style, mood, trope), cast with IMDb links, and every episode's number, link, likes, release time and free flag. Get title ids from reelshort_search, reelshort_home or reelshort_shelf. Only public catalog metadata is returned, never playable video.

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": {
      "id": "<id>"
    },
    "name": "reelshort_movie"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Title id (24 hex characters) from reelshort-home, reelshort-shelf or reelshort-search, or a reelshort.com movie or episode URL

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description is not carrying the safety burden alone. It still adds valuable expectation-setting by clarifying that only public catalog metadata is returned and never playable video, which prevents a common false assumption for a streaming-site tool.

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?

Three tight sentences: what it returns, where ids come from, and what it does not return. The most important constraint (public metadata, no video) is front-loaded alongside the return summary with no filler.

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?

Given an output schema already exists, the returned-field enumeration is partly redundant, but it usefully previews scope and tags/cast/episode coverage. Combined with the id-sourcing hint and the no-video caveat, an agent has everything needed to call it correctly.

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 already documented in the schema with its 24-hex-character format and id sources. The description's mention of those same sibling sources adds little beyond what the schema already states, so this lands at the baseline.

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 ('Get one ReelShort short drama') and enumerates exactly what is returned, including title, description, tags, cast and per-episode data. This differentiates it from the search/home/shelf siblings without the agent needing to open another 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 routes the agent to the three sibling tools that supply title ids (reelshort_search, reelshort_home, reelshort_shelf), which is genuinely actionable context. It stops short of stating explicit when-not-to-use conditions, but the single-id lookup framing makes the boundary clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

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

Need Help?