Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

netshort_title

Retrieve a NetShort title by ID with metadata, site counters, and its current 40-episode window to inspect series details and episode availability.

Instructions

Get one NetShort title with its episode window. Returns one NetShort (netshort.com) title: shortPlayId, library id, name, canonical episode path, cover, synopsis, label list, the site's own like and chase counters (display strings such as 282.6K, not exact integers), publish time, delisted flag, and the episode window the page carries (40 videoEpisodeInfos with episode id, number, lock flag and cover). has_more_episodes reports a full 40-episode window, so a longer series continues past it. An unknown title id is a 404. Play URLs and the site's shortPlayAddress fields are never returned.

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": {
      "title_id": "<title_id>"
    },
    "name": "netshort_title"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoOptional slug from the card URL (the text between /episode/ and the trailing -id); the id resolves the route
title_idYesshortPlayId from any catalogue card or search result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does so well: like/chase counters are display strings (282.6K) rather than exact integers, the 40-episode window is a cap signalled by has_more_episodes, an unknown id yields a 404, and play URLs/shortPlayAddress are deliberately withheld. These are exactly the traits an agent could otherwise misread as complete or numeric data.

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 the action and scope, then supporting detail; every sentence carries information (field inventory, window semantics, error code, deliberate omissions). The field enumeration is long but functional, with little filler.

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 or annotations, so the description must convey both the return shape and the behavioral caveats — and it does: response fields, counter formatting, episode-window truncation, 404 behavior, and excluded URL fields. An agent can call this correctly and interpret the result without further inference.

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% and both parameters are already documented there, including the optional slug being derivable from the card URL and the id being authoritative for routing. The description adds no syntax or format detail beyond that, so baseline 3 applies.

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?

The opening sentence gives a concrete verb and resource ("Get one NetShort title") plus the scope ("with its episode window"), and the field inventory makes clear this is a single-item detail fetch rather than a list. It never names a sibling (e.g. netshort_browse) to draw the boundary explicitly, so it stops just short of the top mark.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the tool returns one title keyed by title_id, which an agent can infer is the follow-up step after a catalogue card or search result. The schema notes where title_id comes from, but the description itself offers no explicit when-to-use/when-not guidance against netshort_search, netshort_browse or netshort_plots.

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