Fetch public video metadata from a Sportskeeda page slug, returning player ID, title, poster, and stream URL for embedding or cataloging.
Get Sportskeeda video metadata. Returns the public video player's ID, title, poster, and stream URL for a video page slug.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Individual Sportskeeda video page path without host |
Changes observed during successful MCP inspections.
v1.17.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It does disclose the returned payload (player ID, title, poster, stream URL), which usefully signals a read-only media-metadata fetch. It does not mention auth needs, rate limits, or behavior when the slug is invalid.
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 action and then the payload, with zero filler. Every clause earns its place.
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 simple single-item read tool with no output schema, the description appropriately lists the returned fields so the agent knows what it gets back and that a stream URL is included. It covers the essentials; only edge-case behavior is missing.
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?
There is one parameter with 100% schema description coverage, so the schema already documents 'slug' as the page path without host. The description adds corroborating meaning ('video page slug') but nothing beyond the schema, making the baseline 3 appropriate.
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 and resource ('Get Sportskeeda video metadata') and further narrows scope to a single video page slug, which implicitly distinguishes it from the plural listing sibling sportskeeda_videos. It does not explicitly name or contrast with that sibling, so it falls short of a 5.
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?
The phrase 'for a video page slug' implies the tool is for resolving one known video page, but there is no explicit when-to-use guidance, no prerequisites, and no named alternative (e.g. sportskeeda_videos for browsing). Usage is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.