Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reelshort_shelf

Fetch a complete ReelShort shelf by ID or URL to get shelf details and every title with cover, link, episode count, tags, plays, and favorites.

Instructions

Get a whole ReelShort shelf. Returns one whole ReelShort shelf, such as TOP (up to 200 titles) or New Release: shelf id, name and every title with its id, title, description, cover, link, episode count, tags, plays and favorites. Shelf ids come from reelshort-home. Only public catalog metadata is read; no playable video is returned.

Input Schema

NameRequiredDescriptionDefault
idYesShelf id from reelshort-home (for example 51003506), or a reelshort.com shelf 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 full burden and does well: it discloses the payload shape (shelf id, name, every title with id/title/description/cover/link/episode count/tags/plays/favorites), a size bound (up to 200 titles), and a scope constraint (public catalog metadata only, no playable video). It stops short of pagination, auth, or rate-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences restate the same idea ("Get a whole ReelShort shelf. Returns one whole ReelShort shelf"), which is wasted space. The remainder is dense and front-loaded with the useful return-field enumeration.

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?

For a one-parameter lookup with no output schema, the description adequately covers what comes back and the read-only, metadata-only nature of the result. Missing only edge-case behavior such as invalid ids, pagination for the 200-title cap, or empty shelves.

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?

Only one parameter, and schema coverage is 100% – the schema already documents the id, its origin in reelshort-home, and URL acceptance. The description's shelf examples (TOP, New Release) add modest meaning about what ids resolve to, but the parameter itself is not explained further.

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 a whole ReelShort shelf") and gives concrete shelf examples (TOP, New Release) with a cap. It also distinguishes itself from reelshort-home by naming it as the id source, so an agent can tell the two apart without opening schemas.

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?

The prerequisite "Shelf ids come from reelshort-home" is a genuinely useful usage cue, but there is no explicit when-to-use/when-not guidance relative to close siblings like reelshort_new_releases, reelshort_tag_books, or reelshort_movie. Usage is implied rather than stated.

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