Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_page_options

Retrieve Sportskeeda page menus, tabs, filters, and select values for a slug to find schedule, ranking, leaderboard, and team navigation links. College-football conference selectors are included.

Instructions

Discover Sportskeeda page menus and filters. Returns the page's live contextual menus, team and ranking links, tabs, schedule views, and every currently offered select-filter value. Leaderboard category and metric values carry their destination slugs. College-football schedule pages expose the client-side conference selector here.

Input Schema

NameRequiredDescriptionDefault
slugYesSportskeeda path without host

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.7/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 burden and does so reasonably: it discloses the live/contextual nature of the menus, that values are page-dependent, that leaderboard category/metric entries include destination slugs, and that college-football schedule pages surface a client-side conference selector here. It omits return format, pagination, or rate-limit behavior, but the output-shape disclosure is genuinely useful context.

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 sentences, front-loaded with purpose followed by return contents, with no wasted wording. The final college-football sentence is narrow but earns its place by flagging a non-obvious page-specific behavior.

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?

For a single-parameter discovery tool with no output schema and no annotations, the description is nearly complete: it explains what menus/filters/links come back and notes page-specific variations. What is missing is sequencing guidance (call this before a filter-consuming tool) rather than return-value detail.

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?

Only one parameter (slug) with 100% schema coverage, and the schema already documents it as 'Sportskeeda path without host'. The description adds no format examples or constraints beyond what the schema supplies, so the baseline of 3 applies.

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: 'Discover Sportskeeda page menus and filters', then enumerates what is returned (menus, team/ranking links, tabs, schedule views, select-filter values). It implicitly contrasts with the sibling sportskeeda_page_data (options/filters vs. content), but never names the sibling explicitly, so the differentiation is left to inference.

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 only implied by the return description – an agent can infer this is a discovery step to enumerate available menus/filters. There is no explicit when-to-use statement, no mention of when not to use it, and no named alternative among the many sibling *_options and *_data tools.

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