Skip to main content
Glama

Crawlora MCP

flickreels_shelf

Read-only

List one page of a curated FlickReels shelf, twelve titles per page, with the shelf's title and own total plus each title's id, movie slug, title, cover, episode count, tags and canonical URL. Take shelf_id from a flickreels_home shelf; the slug is optional because the upstream ignores that path segment. A shelf can hold far more rows than the home page shows, so page through and stop when titles is empty, which the upstream answers as a valid 200 rather than a 404.

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": {
      "shelf_id": "<shelf_id>"
    },
    "name": "flickreels_shelf"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page, default 1. The shelf route pages at 12 items per page; a page past the end is a valid empty page. Compare page against total to know when to stop.
slugNoOptional shelf slug from the same flickreels-home shelf. The upstream ignores the path segment (a wrong slug returns the same shelf) but requires it to be non-empty, so it defaults to shelf.
languageNoOptional locale code, one of: en, ja, ko, tc, es, id, th, de, pt, fr. Defaults to en.
shelf_idYesRequired shelf id from a flickreels-home shelf's id, e.g. 11860. Use the slug from the same shelf when you have it.

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.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the readOnly/openWorld annotations: the upstream ignores the slug path segment, so a wrong slug returns the same shelf, and a page past the end returns a valid 200 with empty titles rather than a 404. Those are exactly the non-obvious facts an agent needs to page safely.

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 core action and page size, then the operational caveats. It is dense and reads as a long run of clauses, but every clause carries real information and nothing is padding.

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?

Covers the source of the required id, paging termination, the ignored slug segment, and the empty-page 200. With an output schema present, the field listing is slightly redundant but nothing an agent needs to call this 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%, so the schema already documents page, slug, language and shelf_id, including the 12-per-page contract and the empty-page behavior. The description mostly restates that, adding only the tie to flickreels_home as the source of shelf_id.

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 and resource ('List one page of a curated FlickReels shelf'), fixes the page size at twelve titles, and enumerates the returned fields. It also distinguishes itself from flickreels_home by saying the shelf_id must be taken from a home shelf.

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 concrete procedural guidance: obtain shelf_id from flickreels_home, page through the shelf, and stop when titles is empty. It does not explicitly say when to prefer a different tool, but the home-shelf dependency establishes the intended workflow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources