Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_page_data

Fetch structured Sportskeeda tables for teams, players, rosters, leaderboards, rankings, depth, playoffs, and game logs using a page slug plus optional season, type, or conference filters.

Instructions

Get Sportskeeda structured sports tables. Returns team, player, roster, leaderboard, ranking, depth, playoff, and game-log tables. NFL team stats include team-leader cards, player-category tables, and Basic, Advanced, and Expert team tables. Season and type are accepted only if offered by the selected page; discover their values with page-options. Player game-log seasons use their discovered season-specific path and return every table offered by the page; NFL category tabs are listed by page-options. College-football schedule slugs accept a discovered conference slug and filter the schedule rows; an offered group with no games on that week returns status no_data. The trade value chart has a separate endpoint. A page with no structured tables returns an upstream error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesSportskeeda path without host
typeNoSeason phase offered by this page's page-options filter; leaderboard pages offer pre, regular, post
seasonNoSeason year offered by this page's page-options filter
conferenceNoCollege-football schedule conference slug from page-options

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.9
    • addedInput schema / properties / conference
      Added value: +{
+  "description": "College-football schedule conference slug from page-options",
+  "enum": [
+    "all-conferences",
+    "all-fbs-i-a",
+    "atlantic-coast",
+    "big-ten",
+    "mid-american",
+    "pac-12",
+    "southeastern",
+    "independents-fbs",
+    "big-12",
+    "conference-usa",
+    "mountain-west",
+    "sun-belt",
+    "aac",
+    "all-fcs-i-aa",
+    "big-sky",
+    "missouri-valley",
+    "ivy-league",
+    "mid-eastern-athletic",
+    "ohio-valley",
+    "patriot-league",
+    "pioneer-league",
+    "southern",
+    "southland",
+    "swac",
+    "northeast",
+    "independents-fcs",
+    "big-south",
+    "caa",
+    "united-athletic"
+  ],
+  "type": "string"
+}
  2. Addedv1.17.7

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden, and it discloses the returned table types, page-options dependency, season-specific path behavior, no_data status, and upstream error for pages without tables. It does not mention auth requirements, rate limits, or pagination behavior, but it provides substantial behavioral context beyond the schema.

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?

The description is dense but front-loaded, starting with the core purpose before moving into return types and constraints. Every sentence adds information relevant to correct invocation, though the amount of detail makes it slightly heavier than a minimal read.

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

Completeness5/5

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

There is no output schema, so the description must explain return values, and it does so by listing the structured table families. It also covers the main operational constraints for a complex tool: parameter discovery through page-options, special college-football filtering, separate trade-values handling, and error behavior.

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 description coverage is 100%, so the baseline is 3, but the description adds meaningful cross-parameter semantics: season and type must be offered by the selected page, conference slugs filter college-football schedules, and player game-log seasons require a discovered season-specific path.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: it gets Sportskeeda structured sports tables. It then enumerates the table categories (team, player, roster, leaderboard, ranking, depth, playoff, game-log), which lets an agent distinguish this tool from sibling data-fetching tools such as page-options and trade-values.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says season and type are accepted only if offered by the selected page and directs the agent to page-options for discovery. It also names the separate trade values endpoint and explains special cases like college-football conference filtering and no_data responses, giving clear when-to-use and when-not-to-use guidance.

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