Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

netshort_home

Retrieve NetShort’s five curated home-page shelves with title IDs, episode paths, covers, synopses, and labels by locale to browse catalogues or feed title and genre lookups.

Instructions

Get NetShort's home shelves. Returns the NetShort (netshort.com) home page's five curated shelves (Trending Now, New Releases, Highly Recommended, Exclusive Originals and one editorial shelf), each with its display name, its "see all" link and 11-12 titles. Every title carries its shortPlayId, library id, name, episode path, cover, synopsis, episode count, finished flag and labels. Pass language to read a different locale's catalogue: the site offers 17 locales and each is a separate library, so shelves and ids differ per locale. Take a title id from any card and pass it to netshort-title; take a label id and name from netshort-genres for netshort-label.

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

Input Schema

NameRequiredDescriptionDefault
languageNoLocale, defaults to en (the un-prefixed default)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does well: it specifies the fixed shelf composition, the per-card field set, and the important behavioral fact that each of the 17 locales is a separate library so shelves and ids differ per locale. It omits any note on auth, rate limits, or whether shelves can be empty for some locales, which is the only meaningful gap for a read-only home endpoint.

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-loads the purpose, then the return shape, then the locale caveat, then the cross-tool routing. The field enumeration is dense but earns its place since there is no output schema; a small amount of compression is still possible in the per-title field list.

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 zero-required-parameter read tool with no annotations and no output schema, the description supplies everything needed: return shape, shelf structure, per-title fields, the locale library caveat, and the follow-up tool routes. Nothing an agent needs to call 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% and the enum already documents the 17 locales, but the description adds real meaning beyond it: passing a language selects a distinct catalogue library whose shelves and ids are not shared with the default. That consequence — ids are locale-scoped and must not be reused across locales — is the semantic an agent actually needs.

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?

Names a specific verb and resource ("Get NetShort's home shelves") and immediately enumerates what comes back: five curated shelves by name, each with display name, see-all link, and 11-12 titles. The scope is concrete enough that an agent can distinguish it from browse/search/toplist siblings without opening the 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?

Gives explicit downstream routing — take a title id to netshort-title, and a label id/name from netshort-genres to netshort-label — which tells the agent how this tool fits in a workflow. It stops short of stating when to prefer this over netshort_browse or netshort_toplist, so the entry-point decision is left implicit.

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