Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reelshort_fandom_posts

List ReelShort Fandom articles newest first, with filters for search text and category plus pagination, returning titles, excerpts, links, images, dates, and categories.

Instructions

List ReelShort Fandom articles. Lists articles from ReelShort's (reelshort.com) editorial site, Fandom, newest first: id, slug, title, excerpt, link, image, publish and modify times and category names, with the total and page count. Filter by search text and by category slug (general-topic, movie-cast-list, top-movie-stories, where-to-watch or where-to-watch-2). Pass an article id to reelshort-fandom-post for its text. Only public editorial text is read.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1 to 10000; defaults to 1
limitNoPage size, 1 to 100; defaults to 10
searchNoText to search articles for, up to 100 characters
categoryNoCategory slug: general-topic, movie-cast-list, top-movie-stories, where-to-watch or where-to-watch-2

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses key behavior: results are newest first, the returned fields are enumerated, total/page count are included, and only public editorial text is read. It does not discuss auth, rate limits, or error behavior, but for a public read-only listing tool the behavior is well communicated.

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?

The description is front-loaded with purpose and scope, then moves efficiently through return fields, filters, sibling routing, and access constraints. The opening two sentences are slightly redundant, but nearly every sentence earns its place.

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?

For a four-parameter, all-optional listing tool with no output schema, the description supplies the missing return-shape context by naming the fields, ordering, total/page count, and filtering options. It also names the sibling tool for full article text, leaving no critical operational gap.

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%, so the schema already fully documents page, limit, search, and category. The description reinforces search and category filtering and repeats the category slug values, but adds little semantic detail beyond the schema 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?

The description states a specific verb and resource: list ReelShort Fandom articles from the editorial site. It explicitly distinguishes this listing tool from the sibling article-text tool, reelshort-fandom-post, so an agent can route correctly 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly says to use this tool for listing and to pass an article id to reelshort-fandom-post for the article text, and it identifies search and category filtering. It does not mention the sibling reelshort_fandom_categories for discovering category slugs, so the guidance is strong but not fully exhaustive.

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