Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_author

Fetch a Sportskeeda author profile by slug or canonical URL to retrieve name, biography, role, image, and listed articles with titles and links.

Instructions

Get a Sportskeeda author profile. Returns a Sportskeeda author's profile, looked up by slug (for example sripad) or canonical url; at least one is required. The response has the name and the articles listed on the profile, each with title and URL, and can also carry biography, role and image_url.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical Sportskeeda /author/<slug> URL; alternative to slug
slugNoSportskeeda author slug, e.g. sripad

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the response shape (name, article list with title/URL, optional biography/role/image_url), which is good return context, but it omits any auth, rate-limit, or error behavior for what is an implied read operation.

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 sentences, front-loaded with the purpose, then the lookup keys, then the return contents. No filler and every clause earns its place.

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?

No output schema exists, so the description appropriately explains the return fields. Combined with full parameter coverage, an agent has enough to call it correctly; only deeper behavioral details are absent.

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 coverage is 100% so the baseline is 3, but the description adds meaningful value: the schema marks required as empty, yet the description clarifies 'at least one is required' and provides a concrete slug example ('sripad'), resolving a genuine ambiguity.

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 a Sportskeeda author profile'), which is clearly distinguishable from the many other *_author siblings by the Sportskeeda brand. It does not explicitly differentiate from sibling tools like sportskeeda_article or sportskeeda_wiki_contributors, but the resource is unambiguous.

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?

The description says a slug or canonical url is required and gives a slug example, implying usage for author lookups. However, it offers no guidance on when to choose this over related Sportskeeda tools (e.g., article or wiki contributors) and no exclusions.

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