Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

netshort_browse

Paginate NetShort's all-episodes browse index 10 titles at a time, returning each page in the site's own browse order with totalCount. Use it when browse ranking matters rather than full-catalogue coverage.

Instructions

List one page of NetShort's browse index. Returns one page of NetShort's (netshort.com) all-episodes browse index: 10 titles per page over the same 11,575-title catalogue as netshort-plots, with the site's own totalCount. It is the same library in the site's browse ordering and a different page size, so it overlaps netshort-plots almost completely — use netshort-plots for coverage and this endpoint when the browse order is what you want; do not merge the two expecting disjoint sets. Pages are 1-based; page 0 is rejected and 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

NameRequiredDescriptionDefault
pageNo1-based page of 10 titles, defaults to 1
languageNoLocale, defaults to en

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does most of it: page size of 10, 1-based pagination, page 0 rejected, out-of-range page yields 404, and the site's own totalCount is returned. It does not address authentication, rate limits, or whether the catalogue ordering can change between calls, which keeps it off 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?

Front-loaded with the core action, then scope, then the sibling differentiation, then paging edge cases. It is dense but each sentence carries information; the overlap warning is slightly restated ("overlaps almost completely" plus "do not merge").

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?

With no output schema, the description does supply the return shape (10 titles per page plus totalCount), which an agent needs. It leaves locale behavior and the fields inside each title entry implicit, but for a two-optional-parameter list tool this is close to sufficient.

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%, so the baseline is 3, but the description adds error semantics the schema lacks (page 0 rejected, page past the end is 404) and confirms page size and catalogue scope. The enum for language is left entirely to the schema with no locale-selection guidance.

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 one page of NetShort's browse index") and immediately contrasts it with the named sibling netshort-plots, including that both cover the same 11,575-title catalogue. An agent can distinguish the two without opening either 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?

Gives an explicit routing rule: use netshort-plots for coverage, use this tool when browse ordering matters, and warns against merging the two expecting disjoint sets. That is a when-to-use, when-not-to-merge, and alternative all in one paragraph.

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