Crawlora MCP

netshort_browse

Read-only

List one page of NetShort's all-episodes browse index: 10 titles per page over the same catalogue as netshort_plots, with the site's own totalCount. Use it only when the browse ordering is what you want: it overlaps netshort_plots almost completely, so do not merge the two expecting disjoint sets. Pages are 1-based; a page past the end is a 404.

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

Input Schema

Name	Required	Description	Default
`page`	No	1-based page of 10 titles, default 1. Page 0 is rejected. A page past the end answers HTTP 404 upstream.
`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.7/5.0

Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description discloses that pages contain 10 titles, that the catalogue overlaps netshort_plots almost completely, that totalCount comes from the site, and that a page past the end returns 404. These are meaningful behavioral details not present in the annotations.

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?

The description is three tight sentences: purpose and page size first, then the sibling-overlap routing rule, then paging/error behavior. Every sentence contributes and nothing is repeated unnecessarily.

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?

Given the output schema and read-only annotations, the description covers what an agent needs: scope, catalogue relationship to netshort_plots, page size, paging behavior, and upstream 404 behavior. No critical gap remains.

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%, so the page and language semantics are already documented in the input schema. The description mentions 1-based paging and the 404 for pages past the end, but those details are also in the schema, so it adds little beyond the structured parameter documentation.

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 states a specific verb and resource: "List one page of NetShort's all-episodes browse index." It adds page size, catalogue source, and the site's totalCount, and explicitly distinguishes the tool from netshort_plots by warning about overlap.

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?

It gives an explicit rule: "Use it only when the browse ordering is what you want". It names the alternative, netshort_plots, and says not to merge the two expecting disjoint sets, which tells the agent when to use this tool and when not to.

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?