Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

netshort_toplist

Retrieve one fixed NetShort toplist board—trending, new releases, recommended, or exclusive originals—as twelve titles without paging for a cheaper single-board read.

Instructions

List one NetShort toplist board. Returns one of NetShort's (netshort.com) four fixed toplist boards: twelve titles with the same card shape as the other catalogue endpoints and no paging. The four boards — trending-short-dramas, new-short-drama-releases, recommended-short-dramas, exclusive-original-short-dramas — are the complete set from the site's own navigation, and each board's titles also appear as a home shelf, so this is the cheaper single-board read. An unknown board is rejected locally.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "board": "<board>"
    },
    "name": "netshort_toplist"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardYesBoard slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.2/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 well: it discloses the fixed result size (twelve titles), the card shape, the absence of paging, that the four boards are the complete set, and that unknown boards are rejected locally rather than by the server. Auth requirements and rate limits are unmentioned, which is the only notable gap.

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?

Purpose is front-loaded in the first sentence, followed by return shape, then board enumeration, then the trade-off versus home shelves — a sensible order with no filler. The board list is long but earns its place because it defines the valid input domain.

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 one-parameter, no-output-schema tool, the description supplies everything needed: what is returned, how many items, that there is no paging, that the board set is closed, and how invalid input behaves. Nothing material is missing for correct invocation.

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 schema already enumerates all four board slugs with a 'Board slug' description, so the parameter is fully specified structurally. The description adds a little meaning by asserting the enum is the complete set drawn from the site's own navigation and that out-of-enum values fail locally, but it does not explain differences in content between boards.

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 opens with a specific verb and resource ('List one NetShort toplist board') and immediately enumerates the four boards it can return, so an agent knows exactly what class of data comes back. It also frames itself against 'the other catalogue endpoints' and the home shelves, making it distinguishable from sibling reads.

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 gives a clear selection rationale: each board's titles also appear as a home shelf, 'so this is the cheaper single-board read' — that tells the agent when this is preferable to a broader catalogue read. It stops short of naming an explicit alternative tool or stating when not to use it, which keeps it out of the top band.

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