Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

flickreels_classify

Lists one page (12 titles) from a FlickReels category by matching tag_id with its slug, returning playlet IDs, titles, covers, episode counts, tags, canonical URLs, and category totals.

Instructions

List one page of a FlickReels category. Returns one page of a FlickReels (flickreels.net) category listing: twelve titles with each one's playlet id, the slug flickreels-movie requires, title, cover, episode count, tags and canonical URL, plus the site's own total for that category. Take tag_id and slug from flickreels-genres for the same locale: the route is slug+id keyed, so an id-only request, a wrong slug and an unknown id are all a 404. Page 0 is treated as page 1 locally because the upstream canonicalises it, and a page past the end is a valid empty page with empty=true and the site's total intact, never an error.

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": {
      "tag_id": "<tag_id>",
      "slug": "<slug>"
    },
    "name": "flickreels_classify"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-based page of 12 titles, defaults to 1
`slug`	Yes	Category slug from flickreels-genres for the same language
`tag_id`	Yes	Category tag id from flickreels-genres; 0 means All
`language`	No	Locale code, defaults to en

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.6/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 whole burden, and it does substantial work: it discloses pagination quirks (page 0 canonicalised to 1 upstream), that an out-of-range page is a valid empty page with empty=true rather than an error, and that the site's total survives past-the-end requests. What it omits is the operational envelope — whether any auth, rate limit, or caching applies — which is a real gap for an unannotated network tool.

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 content is dense and front-loaded — purpose, payload, prerequisite, then error/edge semantics in the right order. There is minor redundancy between the first sentence ("List one page of a FlickReels category") and the opening of the second ("Returns one page of a FlickReels category listing"), which could be merged.

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 output schema, the description correctly takes on the return-shape burden by enumerating the fields an agent will receive and the category total. Combined with the 404 and empty-page rules, an agent has everything needed to construct a valid call and interpret both success and edge-case responses.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description earns more by adding semantics the schema cannot express: the route is slug+id keyed so the two required params must come from the same locale's genres call, and page 0 is accepted and normalised. It does not add much for language beyond the enum already present.

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 opens with a specific verb and resource ("List one page of a FlickReels category") and immediately enumerates the exact payload: twelve titles with playlet id, slug, title, cover, episode count, tags, canonical URL, plus the site's total. It explicitly positions itself against sibling surfaces by naming flickreels-genres as the source of tag_id/slug and flickreels-movie as the consumer of the returned slug.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives an explicit prerequisite chain ("Take tag_id and slug from flickreels-genres for the same locale") and states the precise conditions that produce failure (id-only request, wrong slug, unknown id are all 404). An agent knows to call the genres tool first and knows exactly which combinations are invalid, with no inference required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server