Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

reelshort_fandom_post

Fetch a ReelShort Fandom article by ID, slug, or URL and return its editorial text, metadata, category, image, timestamps, and linked ReelShort title IDs.

Instructions

Get a ReelShort Fandom article. Returns one article from ReelShort's (reelshort.com) editorial site, Fandom: title, excerpt, link, image, publish and modify times, category names, the full article text as plain text, and the ids of the ReelShort titles it links to (pass them to reelshort-movie). id is the article id, its slug, or its reelshort.com/fandom URL. Only public editorial text is read. An unknown article returns not found.

Input Schema

NameRequiredDescriptionDefault
idYesArticle id (digits), article slug, or a reelshort.com/fandom URL

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?

No annotations exist, so the description carries the burden and does well: it discloses the full return shape (title, excerpt, link, image, times, categories, plain-text body, linked title ids), states only public editorial text is read, and specifies the not-found behavior for unknown articles. It stops short of pagination/auth/rate-limit detail, but this is a read of a single public article.

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?

Purpose is stated first, then return fields, then input formats and edge behavior. The field enumeration is long but earns its place because there is no output schema; only minor trimming would be possible.

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?

With no annotations and no output schema, the description supplies everything an agent needs: what is returned, what the id accepts, read-only public scope, not-found behavior, and the cross-tool handoff to reelshort-movie.

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 as 'Article id (digits), article slug, or a reelshort.com/fandom URL'. The description repeats that same information rather than adding new constraints, 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 ('Get') and resource ('ReelShort Fandom article'), then enumerates the returned fields, making clear it is the single-article counterpart to the sibling list tool reelshort_fandom_posts.

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?

Gives clear operational context: id accepts article id, slug, or full reelshort.com/fandom URL, and linked title ids should be passed to reelshort-movie. No explicit 'don't use for X' exclusion, and no pointer back to reelshort_fandom_posts for discovery, which keeps it from a 5.

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