Crawlora MCP

flickreels_home

Read-only

List the shelves the FlickReels home page renders, in the site's own order, with each shelf's column id, slug, title, the site's own total and the titles it rendered. Use this to see what FlickReels is promoting and to find the shelf_id and slug for flickreels_shelf. FlickReels publishes the true count while rendering only a window of rows, so the total can exceed the returned titles.

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	Optional locale code, one of: en, ja, ko, tc, es, id, th, de, pt, fr. Defaults to en; every other locale is served from its own localised home page.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4.2/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 and remote-fetch behavior are covered. The description adds a real behavioral trait beyond the annotations: the site publishes a true count but renders only a window of rows, so total can exceed the returned titles, and the ordering is the site's own. It does not explain whether the shelf set varies by locale beyond what the schema says, which keeps it from 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 action and return shape, then usage, then the caveat about totals. Dense but every sentence carries information; the total-versus-titles caveat is slightly tangled in wording but earns its place.

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?

For a read-only listing tool with a full output schema and complete annotation coverage, nothing an agent needs is missing: purpose, ordering semantics, returned fields, the promoted-content framing, routing to the shelf tool, and the total/rendered discrepancy are all stated.

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 description coverage is 100% and the single language parameter is fully documented in the schema, including the allowed enum values and the default. The description contributes nothing about the parameter, so the 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?

The description opens with a specific verb and resource ("List the shelves the FlickReels home page renders") and enumerates the returned fields (column id, slug, title, total, titles). It explicitly distinguishes itself from the sibling flickreels_shelf by positioning itself as the source of the shelf_id and slug that sibling needs.

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 states a concrete use case ("see what FlickReels is promoting") and names the downstream alternative (flickreels_shelf) plus the values this call provides for it. There is no explicit when-not-to-use guidance, e.g. no note that it is only for the home page versus category or genre listings, but the positive routing is clear.

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

All Crawlora MCP tools Inspect

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

Need Help?