Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

flickreels_movie

Retrieve a FlickReels title’s metadata and complete episode list—including episode numbers, titles, durations, and lock status—by passing its ID and slug; no playable media is returned.

Instructions

Get a FlickReels title with its full episode list. Returns one FlickReels (flickreels.net) title: the site's own title, cover, synopsis, episode count, release date and tag labels, the complete episode list (number, chapter id, title, duration in seconds and locked flag), and the detail page's own related shelf. The route is slug+id keyed, so pass both values from the same card; an id-only request or a wrong slug is a 404. Episode cover images are signed with an expiring token and are deliberately not returned, and no playable media is ever exposed.

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": {
      "title_id": "<title_id>",
      "slug": "<slug>"
    },
    "name": "flickreels_movie"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	Title slug from the same card
`language`	No	Locale code, defaults to en
`title_id`	Yes	Playlet id from any listing card

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the complete returned field set, the slug+id composite keying, the 404 failure mode, and two deliberate omissions (signed expiring episode cover images, no playable media). It stops short of mentioning auth requirements, rate limits, or caching behavior, keeping it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the purpose before the return inventory, then the keying rule, then the exclusions. The return-value enumeration is dense but every clause carries information; no filler or restated title.

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?

There is no output schema, so the description substitutes for it by naming every returned field including the nested episode list members (number, chapter id, title, duration, locked flag). Combined with the keying rule and the explicit 404 condition, an agent has everything needed to call this 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 coverage is 100%, so all three parameters (slug, title_id, language) are already documented in the schema, giving a baseline of 3. The description adds genuine cross-parameter semantics — both values must originate from the same card and id-only fails — which is useful but just above the baseline rather than transformative.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence gives a specific verb and resource: 'Get a FlickReels title with its full episode list', and the second sentence enumerates exactly what a title record contains (synopsis, episode count, tags, episodes, related shelf). This makes the detail-fetch scope clear against listing-style siblings like flickreels_shelf or flickreels_home, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The description states a real precondition — slug and id must come from the same card, and an id-only request or wrong slug yields a 404 — which guides correct invocation. It does not say when to choose this tool over a sibling detail/list tool, so guidance is implied rather than comparative.

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

Deploy Server