Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_videos

List video cards and channel slugs from Sportskeeda's main video library or a given listing slug. Retrieve titles, URLs, thumbnails, and durations for browsing or data collection.

Instructions

List Sportskeeda videos and channels. Lists video cards from Sportskeeda's main video library, or from a listing given by slug (default videos, for example go/epl/videos). Items have a title, slug, URL, and thumbnail, duration and channel when present. The response also lists channels with their slugs. An empty or blocked listing returns an upstream error.

Input Schema

NameRequiredDescriptionDefault
slugNoVideo listing path without host; defaults to videos

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the returned item fields (title, slug, URL, thumbnail, duration, channel) and the channels list, plus the notable 'empty or blocked listing returns an upstream error' behavior. However it omits pagination, result limits, and any read-only/safety context, so disclosure is partial.

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?

Three sentences, purpose front-loaded, no filler. The return-shape sentence is slightly dense but every sentence contributes. Could be tightened but is well organized.

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?

No output schema exists, so the description appropriately describes the returned items and channels. Combined with the slug semantics and error note, an agent has enough to call it correctly; only pagination/limits are unaddressed.

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 value: it restates the default (`videos`) and supplies a concrete example path (`go/epl/videos`), clarifying the expected slug format beyond the schema's terse 'path without host'.

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?

States a specific verb and resource ('List Sportskeeda videos and channels') and clarifies the scope (main library vs. a `slug`-specified listing). It does not differentiate itself from the singular sibling `sportskeeda_video`, leaving the agent to infer the distinction.

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 by 'list' and the slug-based listing behavior, but there is no explicit when-to-use/when-not-to-use guidance and no routing to the closely named `sportskeeda_video` sibling. The agent can infer the scenario but gets no exclusions.

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