Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

flickreels_genres

Retrieve FlickReels category taxonomy and supported languages for a locale, including tag_id and slug values required for classification.

Instructions

List FlickReels' complete category and language taxonomy. Returns the complete FlickReels (flickreels.net) category taxonomy for one locale: every category the site lists, each with the tag_id and slug that flickreels-classify requires, plus the site's own 10-entry language list, which is the value space of the language parameter. This is the discovery endpoint for both the tag_id and language parameters, so no caller has to hard-code them. Category tag ids and slugs are locale-scoped: read both from the same locale you pass to the listing endpoint. The All category is tag_id 0 and its slug is 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
languageNoLocale code, defaults to en

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.3/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 burden and does well: 'List' implies a read, and it discloses that tag ids and slugs are locale-scoped, that the language list is the value space for the language parameter, and that the All category is tag_id 0 with slug 'all'. It stops short of stating response shape or whether results are cached, 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?

The definition is front-loaded: purpose first, then the discovery role, then the locale-scoping caveat, then the All-category detail. There is mild redundancy in restating 'complete category taxonomy' twice in the opening two sentences, but no sentence is wasted overall.

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?

For a zero-required-parameter discovery tool with no annotations and no output schema, the description supplies the return content (categories with tag_id/slug, language list, All category) and the locale coupling rule. The only gap is that the exact response structure isn't described, which matters somewhat given the absence of an output schema.

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 the single parameter already carries an enum and 'defaults to en', so baseline is 3. The description adds real meaning beyond the schema by identifying the language taxonomy as the authoritative value space and warning that category tag ids and slugs are locale-scoped and must match the locale used downstream.

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+resource ('List FlickReels' complete category and language taxonomy') and immediately clarifies scope: one locale, every category the site lists, each with tag_id and slug, plus the 10-entry language list. An agent can distinguish this discovery tool from the listing/classify siblings by its stated output content alone.

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 explicitly positions itself as 'the discovery endpoint for both the tag_id and language parameters, so no caller has to hard-code them,' which tells the agent to call it before flickreels-classify or a listing endpoint. It also advises reading tag ids and slugs from the same locale passed to the listing endpoint. It lacks an explicit when-not-to-use statement, so it falls short of a 5.

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

Deploy Server

Other Tools