Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

flickreels_genres

Read-only

List FlickReels' complete category and language taxonomy for one locale, returning every category's tag_id, display name, slug and listing URL plus the site's own 10-entry language list. Use this first to get the tag_id and slug that flickreels_classify requires; both are locale-scoped, so take them from the same language you browse in, and do not hard-code the 126 categories. The All category is tag_id 0 with slug all.

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_genres"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoOptional locale code, one of: en, ja, ko, tc, es, id, th, de, pt, fr. Defaults to en. Category tag ids and slugs are locale-scoped, so take both from the taxonomy of the same locale you pass to flickreels-classify.

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.7/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 is covered; the description adds non-obvious behavioral facts: the taxonomy is locale-scoped, the full category set should be discovered rather than hard-coded, and the All category is a fixed tag_id 0 / slug 'all' sentinel. It stops short of describing pagination or whether the response is cached/static, but the key behavioral caveats are present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three tight sentences, front-loaded with what the tool returns, followed by the routing rule and then the sentinel detail. No filler, and the actionable guidance precedes the trivia.

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?

An output schema exists so return values need no explanation, and the single optional parameter is fully documented in the schema. The description covers the remaining agent-relevant concerns: call ordering relative to the sibling, locale consistency, and the hard-coding trap.

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% and already lists the allowed locale codes and the en default, so the baseline would be 3. The description adds real meaning beyond the schema by explaining the consequence of the choice: tag_ids and slugs are locale-scoped and must match the locale later passed to flickreels_classify.

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 FlickReels' complete category and language taxonomy for one locale') and enumerates the returned fields (tag_id, display name, slug, listing URL) plus the 10-entry language list. It is clearly distinguishable from flickreels_classify, which it names as the downstream consumer of its output.

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?

Gives explicit ordering guidance ('Use this first to get the tag_id and slug that flickreels_classify requires'), an exclusion ('do not hard-code the 126 categories'), and a correctness rule ('both are locale-scoped, so take them from the same language you browse in'). An agent knows both when to call it and how to use the result.

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

All Crawlora MCP toolsInspect
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