Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

netshort_search

Search NetShort's catalogue by keyword to retrieve locale-specific short drama results with IDs, titles, covers, synopsis, and episode counts for discovery or deduplication.

Instructions

Search NetShort's catalogue by keyword. Returns one page of NetShort (netshort.com) keyword search results: each match's shortPlayId, library id, name with the upstream's highlight markup stripped, episode path, cover, synopsis, episode count and labels. This is the platform's only real search — its /search page ships just the site shell — and it is reached through the site's own encrypted XHR, with the key material read from the site's public bundle at runtime and never pinned. The search is fuzzy, not exact: an unmatched keyword still returns token matches, so treat results as approximate and never read an empty result as "no such title" (only an empty query is empty, and that is rejected locally). Pages are not a strict partition either — page 2 repeated 2 of page 1's 15 ids in the 2026-11-07 measurement — so dedupe by id when accumulating pages. The upstream applies a floor of 15 items on page 1, so a response can carry more results than page_size. language selects the locale and results are locale-specific.

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": {
      "query": "<query>"
    },
    "name": "netshort_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based result page, defaults to 1
queryYesKeyword to search for
languageNoLocale sent as content-language; results are locale-specific
page_sizeNoResults per page, 1-50, default 10; the upstream floors page 1 at 15 items

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the encrypted XHR transport with runtime-read key material, fuzzy token matching, overlapping pages (page 2 repeating page 1's ids in a dated measurement), a 15-item floor on page 1, locale-specific results, and local rejection of empty queries. These are non-obvious behaviors an agent could not infer from the schema.

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 purpose and return shape, then layered constraints in descending importance; every sentence carries operational information. Some sentences are long and pack multiple clauses (transport detail plus measurement caveat), which slightly slows scanning but wastes little.

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?

There is no output schema, and the description compensates by listing the returned fields and explaining the paging, dedupe, and floor quirks that govern accumulation. For a four-parameter search tool with no annotations, nothing an agent needs in order to call and consume it correctly is missing.

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 real meaning beyond it: page_size can be exceeded because of the upstream 15-item floor on page 1, and language changes which locale's results come back. It does not explain page semantics beyond the schema's "1-based result page," but the added constraints lift it above baseline.

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 ("Search NetShort's catalogue by keyword") and enumerates exactly what a result carries (shortPlayId, library id, name, episode path, cover, synopsis, episode count, labels). It also stakes out scope by declaring this "the platform's only real search," which separates it from the browse/genres/title siblings without needing their names.

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?

Gives clear when-to-use context and explicit when-not semantics: results are fuzzy, an empty result must not be read as "no such title," and pages must be deduped by id when accumulating. It does not explicitly route to siblings such as netshort_title for exact lookups, which keeps it short of a 5.

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