Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sportskeeda_taxonomy_search

Search Sportskeeda categories, events, teams, players, wiki pages, and wiki tags using a short keyword query. Use it to find matching taxonomy entities from the site's anonymous frontend search.

Instructions

Search Sportskeeda categories and entities. Calls Sportskeeda's anonymous frontend taxonomy search across categories, events, teams, players, wiki pages, and wiki tags. The upstream UI always searches all six types; the q phrase is sanitized and capped at 100 characters just like the site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch phrase; punctuation is replaced with spaces and the result is capped at 100 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

B3.2/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 that this calls an anonymous frontend taxonomy search, always searches all six entity types, and sanitizes input, but it does not describe result format, pagination, or other operational constraints.

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 three sentences and front-loads the core purpose. Some of the input-sanitization detail is redundant with the schema, but it is not bloated and remains easy to scan.

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 one-parameter search tool with no output schema and no annotations, the description covers the searchable domain and input handling but stops short of describing what results look like. An agent can call it, but it lacks return-shape context that would be helpful without an output schema.

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 single q parameter is already documented in the schema. The description repeats the sanitization and 100-character cap behavior rather than adding new meaning beyond what the schema provides.

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 ('Search Sportskeeda categories and entities') and enumerates the six searchable entity types, so an agent can tell what the tool does. It does not explicitly differentiate itself from sibling Sportskeeda tools such as sportskeeda_sections or sportskeeda_article, which keeps it just below a 5.

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

Usage Guidelines2/5

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

The description explains what the tool searches but gives no explicit guidance on when to use it instead of alternatives. There are no when-to-use conditions, no exclusions, and no named sibling tools despite a large set of Sportskeeda siblings.

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