Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

reelshort_shelf

Read-only

Get one whole ReelShort shelf (for example TOP with up to 200 short dramas, or New Release) and return every title's id, title, description, cover, link, episode count, tags, plays and favorites. Get shelf ids from reelshort_home. 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": {
      "id": "<id>"
    },
    "name": "reelshort_shelf"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesShelf id from reelshort-home (for example 51003506), or a reelshort.com shelf URL

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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and network scope are covered. The description adds that only public catalog metadata is returned (no user data) and that a shelf can hold up to 200 titles, which is useful sizing context, but it says nothing about pagination, empty shelves, or failure behavior.

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 verb and scope, then the id source, then a data-provenance note; no filler sentences. The enumerated return-field list is somewhat long and partly redundant with the output schema, which keeps it from a 5.

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?

With an output schema present, return values need not be re-explained, and the prerequisite plus public-metadata note cover the main gaps for a simple one-param fetch. Only edge cases (empty or missing shelf, result size limits beyond "up to 200") are unaddressed.

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 description coverage is 100% and the single id parameter is fully documented in the schema, including the URL alternative and an example value. The description only echoes "Get shelf ids from reelshort_home," 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 ("Get one whole ReelShort shelf") and gives concrete shelf examples (TOP with up to 200 titles, New Release) plus an enumeration of returned fields. An agent can tell this apart from reelshort_home (which supplies shelf ids) and reelshort_movie (single title) without opening a 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?

Explicitly states the prerequisite: "Get shelf ids from reelshort_home," naming the sibling that produces the required input. It gives clear context but does not state when this tool should not be used, so it falls just short of a full when/when-not rule set.

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