Crawlora MCP

netshort_home

Read-only

List NetShort's five curated home shelves (Trending Now, New Releases, Highly Recommended, Exclusive Originals and one editorial shelf) with each shelf's display name, see-all link and 11-12 short-drama titles carrying shortPlayId, library id, name, episode path, cover, synopsis, episode count, finished flag and labels. Use it to discover titles and to pick a shortPlayId for netshort_title. language selects one of the site's 17 locale catalogues; each locale is a separate library, so ids and shelves differ per locale.

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

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

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description still adds real substance: a fixed count of five shelves, 11-12 titles per shelf, and the warning that each locale is a separate library so ids and shelves differ. It also notes unknown locale values are rejected locally, which is useful pre-call behavior.

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 description is front-loaded with the core purpose before the field list and locale caveat. It is dense and packs a long enumeration into a single sentence, but nothing is redundant with the schema or annotations.

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?

An output schema exists, so return values need no further explanation, and the single optional parameter is fully documented. What remains unaddressed is minor: there is no mention of rate limits, caching or whether the shelf composition changes over time, but none of that blocks a correct call.

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 enum already lists all 17 locales plus the default, so the schema does the heavy lifting. The description still adds meaning the schema cannot: that locale selects one of 17 separate catalogues and that identifiers are not stable across locales, which changes how an agent should pass and reuse ids.

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?

Specific verb and resource: "List NetShort's five curated home shelves", with the shelves named and the payload fields enumerated. It also states the follow-on use ("pick a shortPlayId for netshort_title"), which separates it from the individual-title sibling.

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?

Gives a clear when-to-use: discovering titles and harvesting a shortPlayId to feed netshort_title. It does not explicitly say when to prefer netshort_browse, netshort_search or netshort_toplist instead, so routing among the other discovery siblings is left to inference.

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?