List public Sportskeeda video cards and channels from the main library or a sport/event listing; pass an optional slug to target a specific page.
List Sportskeeda videos and channels. Lists public video cards from the main video library or a sport/event video listing.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | No | Video listing path without host; defaults to videos |
Changes observed during successful MCP inspections.
v1.17.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. 'Public video cards' implies no authentication is required, which is useful, but pagination, result count, and return format are undisclosed for a list endpoint.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the core action. The second sentence partly restates the first verb ('List'/'Lists') but does add the channel and two-mode scope, so waste is minimal.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter list tool with no output schema, the description covers purpose and rough scope but omits return shape and pagination behavior. Adequate but leaves gaps an agent might want filled.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single slug parameter is fully documented there, including its default of 'videos'. The description only loosely reinforces the two listing paths, adding little beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List') and resource ('Sportskeeda videos and channels'), and distinguishes the listing tool from the detail sibling sportskeeda_video by describing it as returning cards from a library or listing. However it does not explicitly name or contrast with that sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It hints at two modes ('main video library or a sport/event video listing') but gives no explicit when-to-use guidance, no mention of when to prefer sportskeeda_video instead, and no prerequisites. The agent must infer the routing from the slug parameter.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.