Skip to main content
Glama

sportskeeda_videos

Read-only

List public Sportskeeda video-card records from the main library or a sport/event video page. Use sportskeeda_video for one video, sportskeeda_feed for its editorial feed, or sportskeeda_sitemap_items to discover URLs.

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": "sportskeeda_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoVideo listing path without host; defaults to videos

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / slug / description
      Added value: +"Video listing path without host; defaults to videos"
  2. First observed

TDQS

A3.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint and openWorldHint. The description adds little behavioral context beyond 'public' – no pagination behavior, no return shape details, no rate limits. With annotations covering the safety profile, the bar is lower, but the description offers essentially no additional behavioral disclosure.

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 sentences, front-loaded with the primary action and followed by sibling routing. Zero waste.

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?

Output schema exists, so return values need not be explained. The description covers purpose, scope, and sibling routing, which is sufficient for a read-only filtered-list tool with full schema coverage. Minor gap in pagination behavior, but not critical for this tool class.

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 coverage is 100%, so the schema already documents the single 'slug' parameter fully. Baseline 3 is appropriate since the schema does the heavy lifting and the description adds no param-specific meaning beyond implying the listing path.

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 public Sportskeeda video-card records.' The scope qualifier 'main library or a sport/event video page' distinguishes it from the single-video and feed tools. It doesn't name the exact sibling list tool that may also list videos, but it's clearly distinguishable.

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?

Explicitly names three siblings (sportskeeda_video, sportskeeda_feed, sportskeeda_sitemap_items) and the condition selecting each. Strong routing guidance. No explicit 'when not to use' beyond the sibling routing, which is likely sufficient here.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.