Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_video

Retrieve Sportskeeda video metadata from a host-free slug, including ID, title, poster image, stream URL, and description when available.

Instructions

Get Sportskeeda video metadata. Returns metadata for one Sportskeeda video page by host-free slug, such as cricket/sunil-naraine-batting-cpl: its id, title, poster image, stream URL and, when available, a description. A page without a video player returns an upstream error, and stream availability can depend on geography.

Input Schema

NameRequiredDescriptionDefault
slugYesIndividual Sportskeeda video page path without host

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.5/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 burden and does well: it discloses the error case (a page without a video player returns an upstream error) and the geography-dependent limits on stream availability. It stops short of detailing response shape nesting or rate/auth behavior, but the failure modes it does surface are exactly the ones an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the purpose, then return fields and caveats in descending priority. No filler or restatement of the tool name.

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 single-parameter read tool with no output schema and no annotations, the description covers purpose, input format with example, returned fields, and failure/availability caveats. Nothing material for correct invocation 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 already 100%, so the baseline would be 3, but the description goes beyond it by defining the slug as 'host-free' and supplying a worked example (`cricket/sunil-naraine-batting-cpl`) that clarifies the expected path format in a way the schema text does not.

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 (get one Sportskeeda video's metadata) and scopes it to a single page addressed by slug, which cleanly separates it from the sibling sportskeeda_videos listing tool. The enumerated return fields (id, title, poster, stream URL, description) make the deliverable unambiguous.

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?

The description makes the precondition clear ('one Sportskeeda video page by host-free slug') and gives a concrete slug example, so an agent knows what input shape is required. It does not, however, explicitly name sportskeeda_videos as the alternative for browsing/listing videos, nor state when not to use this tool.

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