Crawlora MCP

reelshort_fandom_posts

Read-only

List articles from ReelShort's Fandom editorial site (actor profiles, plot write-ups, streaming guides), newest first, with each article's id, title, excerpt, link, image, dates and categories plus total and page count. Filter by search text and by category slug from reelshort_fandom_categories. Use reelshort_fandom_post for an article's text.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reelshort_fandom_posts"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number, 1 to 10000; defaults to 1
`limit`	No	Page size, 1 to 100; defaults to 10
`search`	No	Text to search articles for, up to 100 characters
`category`	No	Category slug: general-topic, movie-cast-list, top-movie-stories, where-to-watch or where-to-watch-2. Documented values: general-topic, movie-cast-list, top-movie-stories, where-to-watch, where-to-watch-2.

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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuine behavior beyond that — newest-first ordering, the returned field set, and total/page count for pagination. It does not mention rate limits or authentication, which keeps it short of a 5.

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 sentences, front-loaded with the resource and its scope, then filtering, then the sibling handoff. Nothing is repeated from the schema and no sentence is wasted.

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?

An output schema exists, so return values need no prose explanation, and all four parameters are documented in the schema. With read-only/open-world annotations present, the description covers everything an agent needs to select and call this tool 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 description coverage is 100%, so the schema already fully documents page, limit, search and category; baseline is 3. The description adds only marginal meaning by pointing out that category slugs should come from reelshort_fandom_categories, which is a useful provenance hint but not expanded semantics.

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?

Specific verb (List) plus a precisely scoped resource: articles from ReelShort's Fandom editorial site, with the content types enumerated (actor profiles, plot write-ups, streaming guides). It also names the two nearby siblings it is not — reelshort_fandom_categories for slugs and reelshort_fandom_post for full text.

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?

States the two filtering modes (search text, category slug sourced from reelshort_fandom_categories) and explicitly routes full-article retrieval to reelshort_fandom_post. Clear usage context, though there is no explicit 'when not to use' condition such as preferring reelshort_search for non-editorial content.

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?