Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

reelshort_fandom_post

Read-only

Get one article from ReelShort's Fandom editorial site by id, slug or URL and return its title, excerpt, link, image, dates, categories, full text and the ReelShort title ids it links to (usable with reelshort_movie). Get ids from reelshort_fandom_posts. An unknown article returns not found.

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_fandom_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesArticle id (digits), article slug, or a reelshort.com/fandom 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

A4.1/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 genuinely new behavior: the not-found outcome for unknown articles and the fact that returned ReelShort title ids are directly usable with reelshort_movie. No contradiction with the read-only annotation.

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 routing hint and the error behavior. The long enumerated field list is the only fat, and since an output schema already exists that list is partly redundant.

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 covering return values and annotations covering safety, the description only needed to supply identifier sourcing and error semantics — both present. Nothing blocking an agent from calling it correctly is missing.

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's schema description already lists digits, slug, or a reelshort.com/fandom URL. The description repeats the same enumeration without adding format examples, precedence rules, or normalization behavior, so 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?

Specific verb (Get) plus precise resource (one article from ReelShort's Fandom editorial site) and the accepted identifier forms. It is clearly distinguishable from the sibling listing tool reelshort_fandom_posts, which it names as the id source.

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 explicitly routes discovery to reelshort_fandom_posts ("Get ids from reelshort_fandom_posts") and names reelshort_movie as the consumer of the linked title ids, so the workflow position is clear. It does not state explicit exclusions, but the detail-vs-list split is unmistakable.

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