Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_feed

Fetch public article cards from any Sportskeeda section, event, team, or player slug. Use optional page pagination only when the source supports it.

Instructions

Get articles from a Sportskeeda section or topic. Fetches the public article cards for a Sportskeeda section, event, team-news, or player-news slug. Page pagination is accepted only when the source advertises it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoSource page, for feeds with pagination; defaults to 1
slugYesSportskeeda path without host, such as wwe, go/epl, or player/jannik-sinner/news

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that it returns public article cards and that pagination is only honored when the source advertises it, but says nothing about auth/permission needs, rate limits, or what happens when pagination is unsupported.

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 short sentences, front-loaded with the core action and no filler. The first two sentences overlap somewhat ('section or topic' vs 'section, event, team-news, or player-news slug'), a minor redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-output-schema, no-annotation read tool, the description is adequate but thin: it doesn't characterize the returned article cards or how many come back per page, which an agent would need to plan paging.

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 both parameters with examples. The description adds a modest gloss by naming the slug categories it accepts, but no additional syntax or format detail beyond the schema, so the baseline 3 is appropriate.

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 (get articles from a Sportskeeda section/topic) and enumerates the accepted slug categories (section, event, team-news, player-news), which helps separate it from siblings like sportskeeda_article and sportskeeda_sections. It does not name those siblings explicitly, so differentiation is inferred rather than stated.

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 the slug enumeration ('section, event, team-news, or player-news slug'), giving an agent a rough sense of when this feed applies, but there is no explicit when-to-use-vs-alternative guidance against sportskeeda_sections, sportskeeda_news, or sportskeeda_article.

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