Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_subcategory

Retrieve a single Kick category by slug to get its ID, name, parent, tags, description, viewers, followers, maturity flag, banner, and kick.com link; unknown slugs return not found.

Instructions

Get one Kick category. Returns one Kick game or activity category by slug: id, name, parent category, tags, description, current viewers, follower count, mature flag, banner and kick.com link. slug comes from kick-subcategories or kick-search-categories. An unknown slug returns not found.

Input Schema

NameRequiredDescriptionDefault
slugYesCategory slug from kick-subcategories' or kick-search-categories' own slug field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.2/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 a good job of disclosing the return shape and the 'not found' behavior for unknown slugs. It does not explicitly state that the operation is read-only, but 'Get' and the field list strongly imply a non-mutating lookup.

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 front-loaded with purpose and return fields, and each sentence generally earns its place. There is minor redundancy between 'Get one Kick category' and 'Returns one Kick game or activity category by slug', but the overall structure is efficient.

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?

For a one-parameter read lookup with no output schema, the description supplies the needed field list, the source of the slug, and the unknown-slug error behavior. Nothing essential for correct invocation is missing.

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 coverage is 100%, so the slug parameter is already well documented in the schema. The description adds that the slug comes from 'kick-subcategories' or 'kick-search-categories', but this largely repeats the schema's own parameter description rather than adding new semantic detail.

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 uses a specific verb and resource ('Get one Kick category') and immediately clarifies that it returns a single game or activity category by slug. It distinguishes the detail lookup from listing/search siblings by naming 'kick-subcategories' and 'kick-search-categories' as slug sources.

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?

The description clearly implies the usage pattern: call this tool with a slug obtained from 'kick-subcategories' or 'kick-search-categories'. It also states the failure behavior for unknown slugs, but it does not give explicit when-not-to-use guidance or name alternatives for listing categories.

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