Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

kick_subcategory

Read-only

Get one Kick game or activity category by slug and return its id, name, parent category, tags, description, current viewers, follower count and link. Use this when you have a slug from kick_subcategories or kick_search_categories and need its numeric id or audience size; an unknown slug returns not found.

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>"
    },
    "name": "kick_subcategory"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description still adds the useful lookup-miss contract ('an unknown slug returns not found'). It stops short of noting rate limits, caching freshness of viewer/follower counts, or whether slugs are case-sensitive.

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 action and payload, followed by the selection rule and edge case. No filler, and each clause carries selection-relevant information.

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 the enumerated return fields are slightly redundant, but they usefully signal that viewer/follower counts are available. Everything an agent needs to decide and call correctly is present; only freshness/staleness of live audience metrics is unaddressed.

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% and the schema already says the slug comes from kick-subcategories' or kick-search-categories' slug field, so the description largely restates it. The only added signal is the invalid-slug outcome, which is marginal above baseline.

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?

A specific verb-plus-resource statement: fetch a single Kick game/activity category by slug, with an enumerated payload (id, name, parent category, tags, viewers, followers, link). This clearly separates it from kick_subcategories and kick_search_categories, which are list/search tools.

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

Usage Guidelines5/5

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

Explicitly states the trigger condition ('when you have a slug from kick_subcategories or kick_search_categories') and the two concrete needs it satisfies (numeric id, audience size). The not-found behavior for an unknown slug completes the guidance.

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

All Crawlora MCP toolsInspect
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