Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

netshort_label

Fetch one page of NetShort label listings—24 titles plus total count—using label_id and name from netshort-genres; page is 1-based.

Instructions

List one page of a NetShort label listing. Returns one page of one NetShort (netshort.com) label listing: 24 titles per page with the site's own totalCount for that label, in the same card shape as netshort-plots. Take label_id and name from netshort-genres — the site's own label path is /drama/--2 and carries both, so a type-2 label id without its name is rejected locally. Label pages are English-only in practice regardless of the site's locale prefixes. Pages are 1-based; page 0 is rejected and a page past the end is a 404.

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": {
      "label_id": "<label_id>",
      "name": "<name>"
    },
    "name": "netshort_label"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	labelName of the same label from netshort-genres; it is part of the site's own path
`page`	No	1-based page of 24 titles, defaults to 1
`label_id`	Yes	Type-2 labelId from netshort-genres

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does substantial work: page size of 24, inclusion of the site's own totalCount, English-only label pages in practice, 1-based paging, page 0 rejected, and a past-the-end page returning 404. It does not mention permissions, rate limits, or whether results are cached, which keeps it from 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?

Content is front-loaded and dense with no filler, but the opening two clauses restate each other ("List one page of a NetShort label listing" then "Returns one page of one NetShort (netshort.com) label listing"), which is mild redundancy. The remaining clauses each contribute a distinct constraint.

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?

There is no output schema, so the description must describe the return, and it does: 24 titles per page, the site's own totalCount, and a card shape matching netshort-plots. That cross-reference assumes knowledge of the other tool, and pagination termination beyond the 404 is unstated, leaving small gaps for a 3-parameter read tool.

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, and the description adds real meaning on top: label_id is a type-2 id whose companion name is mandatory (local rejection otherwise), and the page parameter's boundary behavior (0 rejected, past-end 404) goes beyond the schema's "1-based, defaults to 1".

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 a NetShort label listing"), fixes the page size at 24 titles, and names the sibling netshort-genres as the source of the identifying pair and netshort-plots as the card-shape equivalent. An agent can distinguish this from netshort_genres and netshort_plots without opening any schema.

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 concrete routing rule: obtain label_id and name from netshort-genres, because a type-2 label id without its name is rejected locally. That is clear when-to-use context, but there is no explicit statement of when to prefer this over netshort_browse or netshort_search, so it stops short of full alternative coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server