Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

netshort_plots

List one page of NetShort’s complete catalogue in plot-index order, 24 titles per page, and walk consecutive pages by locale to browse the full library.

Instructions

List one page of NetShort's whole catalogue. Returns one page of NetShort's (netshort.com) complete catalogue in the site's plot-index order: 24 titles per page with the site's own totalCount (11,575 titles in the 2026-11-07 capture), page number and page size. Use it to walk the whole library; consecutive pages do not overlap. Pages are 1-based path segments: page 1 is the canonical un-suffixed URL and page 0 is rejected locally. A page past the end answers HTTP 404 upstream, so has-next is only ever a full-page signal — walk until a 404. Pass language for one of the site's 17 locale catalogues.

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

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page of 24 titles, defaults to 1; a page past the end is a 404
languageNoLocale, defaults to en

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does it well: fixed 24-per-page size, site ordering, totalCount passthrough, 1-based path segments, page 0 rejected locally, out-of-range pages returning upstream HTTP 404, and the warning that has-next is only a full-page signal. These are the non-obvious mechanics an agent needs before paginating.

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 what the tool returns, then pagination mechanics, then parameters; sentences are dense but purposeful. The snapshot count "11,575 titles in the 2026-11-07 capture" is perishable trivia that is nearly the only removable material.

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 compensates by naming the returned envelope (titles page, totalCount, page number, page size). What is still missing is any hint of per-title fields, so an agent knows the shape of the row but not its contents.

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 description coverage is 100%, so the baseline applies. The description reinforces page semantics (page 0 rejected, past-end 404) and adds that language selects one of 17 locale catalogues, but most of that is already in the enum and property descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List one page of NetShort's whole catalogue" gives a specific verb and a precisely scoped resource: exhaustive enumeration, not a filtered or search view. The scope word "whole" implicitly separates it from netshort_search/netshort_browse, but no sibling is named, so it stops short of the top tier.

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 states the intended use ("walk the whole library"), the non-overlap guarantee between consecutive pages, and the exact termination condition ("walk until a 404"). It does not say when to prefer a different tool, e.g. that a known title should go to netshort_title or a keyword to netshort_search.

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