Crawlora MCP

sportskeeda_sitemap_items

Read-only

List canonical Sportskeeda page URLs and modification times from a discovered sitemap, one bounded page at a time. Provide a slug from sportskeeda_sitemaps and optional offset/limit; sitemap_url remains an alternative.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "Slug": "<Slug>",
      "SitemapURL": "<SitemapURL>",
      "Offset": "<Offset>",
      "Limit": "<Limit>"
    },
    "name": "sportskeeda_sitemap_items"
  }
}

Input Schema

Name	Required	Description
`Slug`	Yes	Sitemap slug returned by /sportskeeda/sitemaps; preferred
`Limit`	Yes	Page size from 1 to 500; defaults to 100
`Offset`	Yes	Zero-based item offset
`SitemapURL`	Yes	Exact sitemap URL; alternative to slug

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 7, 2026
- addedInput schema / properties / Limit / description
```
Added value: +"Page size from 1 to 500; defaults to 100"
```
- addedInput schema / properties / Offset / description
```
Added value: +"Zero-based item offset"
```
- addedInput schema / properties / SitemapURL / description
```
Added value: +"Exact sitemap URL; alternative to slug"
```
- addedInput schema / properties / Slug / description
```
Added value: +"Sitemap slug returned by /sportskeeda/sitemaps; preferred"
```
First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context: results come 'one bounded page at a time', signaling pagination that the annotations do not convey.

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 tight sentences, front-loaded with what is returned and how it is paged, followed by the input guidance. No filler.

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?

An output schema exists, so return values need no explanation. The description covers source, paging, and input alternatives; the only wrinkle is that the schema lists Offset/Limit as required while the description calls them optional, a minor mismatch not addressed in the text.

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 description coverage is 100%, so the schema already documents Slug, Offset, Limit, and SitemapURL. The description reinforces the slug/sitemap_url relationship but adds little beyond the schema's 'preferred' and 'alternative to slug' notes, so the baseline 3 applies.

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?

States a specific verb (list) and resource (canonical Sportskeeda page URLs plus modification times) and ties it to an upstream source ('from a discovered sitemap'). It implicitly distinguishes itself from the sibling sportskeeda_sitemaps, which produces the sitemap this tool consumes.

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?

It explains the workflow (get a slug from sportskeeda_sitemaps) and clarifies the slug-vs-URL choice ('sitemap_url remains an alternative'). No explicit when-not guidance, but the routing between the two inputs and the prerequisite tool is clear.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?