Crawlora MCP

netshort_genres

Read-only

List NetShort's label taxonomy: four navigation tabs (all-plots, story, characters, settings) and every label underneath them, each with its labelId, labelName, site path and play count. Use this first to get a label id and name for netshort_label; do not hard-code the set. The 2026-11-07 capture held 196 labels over the four tabs, and three tabs stop at exactly 50, which is upstream's own per-tab cap: capped=true reports that, so treat the list as the site's complete navigation rather than a provably exhaustive vocabulary.

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": "netshort_genres"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Locale, one of: en (default, un-prefixed), ar, cn, de, es, fr, hi, id, it, ja, ko, ms, pt, th, tr, vi, zh. Each locale is a separate catalogue; an unknown value is rejected locally.

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

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real disclosure burden and does so well: it reveals upstream's per-tab cap of 50, the capped=true signal, the 2026-11-07 capture provenance and the resulting caveat that the list is complete navigation but not a provably exhaustive vocabulary. The only weakness is that it explains return-value semantics that the output schema likely already covers, so a small amount of this overlaps structured data.

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 purpose, then usage, then the data caveat, and no filler. The final sentence is long and packs several facts (count, cap, capped flag, interpretation) into one breath, which costs some readability but every clause is load-bearing.

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 single optional-parameter, read-only listing tool with an output schema, this covers purpose, sequencing, and the one genuine trap (per-tab caps making the list look truncated). An agent has everything needed to call it correctly and interpret the result.

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 its full locale enum and its rejection behavior. The description adds nothing about the parameter, not even that each locale yields a different catalogue, so the baseline of 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?

Opens with a specific verb and resource ('List NetShort's label taxonomy') and immediately enumerates the structure returned: four named navigation tabs and, under each, labels carrying labelId, labelName, site path and play count. That is enough for an agent to distinguish it from netshort_label, netshort_plots or the other *_genres siblings without opening the schema.

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?

Explicitly sequences the tool against its alternative: 'Use this first to get a label id and name for netshort_label; do not hard-code the set.' That names the downstream tool and the condition that selects it, which is exactly the routing guidance an agent needs.

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?