Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

flickreels_home

List the shelves rendered on the FlickReels home page with each shelf’s column ID, slug, title, site count, and displayed titles. Use the IDs and slugs to page shelves that carry more items.

Instructions

List the FlickReels home page's shelves. Returns every shelf the FlickReels (flickreels.net) home page renders, in the site's own order: each shelf's column id, the slug flickreels-shelf needs when the row links a see-more page, its title, the site's own count and the titles it rendered. Five shelves are observed for the default locale. The site publishes the true count while rendering only a window of rows, so the count and the returned list length legitimately differ; use flickreels-shelf with the shelf id to page a shelf that carries more.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flickreels_home"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Locale code, defaults to en

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and it delivers the one non-obvious behavior that would otherwise cause errors: the published count and the returned row list legitimately differ because the site renders only a window of rows. It also discloses ordering (site's own order) and the observed shelf count for the default locale. Auth, rate limits, and freshness/caching are not addressed, keeping it off 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?

Purpose is front-loaded in the first clause, then return fields, then an important caveat, then the routing hint — a sensible order. It is dense and longish, and the field enumeration would be redundant if an output schema existed, but with none present that text earns its place.

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?

No output schema exists, so describing the returned fields, ordering, and the count-vs-length discrepancy is exactly what an agent needs to interpret results correctly, and the paging handoff closes the loop. It is nearly complete for a read-only listing call; only per-locale coverage and access requirements remain unstated.

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 language parameter is already documented with an enum and an "defaults to en" note. The description contributes only indirectly, via "Five shelves are observed for the default locale," which hints that locale changes results without spelling out per-locale behavior. Baseline 3 is right when the schema does the lifting.

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?

Opens with a specific verb+resource ("List the FlickReels home page's shelves") and immediately enumerates what each shelf record contains. It is distinguishable from flickreels_shelf, which is named later as the row-paging tool, so an agent can pick between the two without opening a schema.

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?

States an explicit routing rule and its condition: "use flickreels-shelf with the shelf id to page a shelf that carries more." That covers the main fork an agent would face here. It stops short of explicit when-not guidance (e.g., when a fixed list of shelf ids is already known and this discovery call can be skipped).

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

Deploy Server