Crawlora MCP

kick_category_clips

Read-only

List the newest clips made in a Kick game or activity category (for example just-chatting or grand-theft-auto-v), 20 per page, with each clip's title, link, thumbnail, views, likes, duration and source channel. Use next_cursor for the next page; get category slugs from kick_subcategories. A top-level category such as games 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_category_clips"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Category slug from kick-subcategories or kick-search-categories, lowercase; a kick.com/category URL is also accepted
`cursor`	No	Previous response's next_cursor; omit for the newest page

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.

AddedOct 26, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only and open-world, so the description is free to add operational detail: 20 items per page, cursor-based pagination via next_cursor, and the not-found behavior for top-level slugs. That error-mode disclosure is genuinely useful context beyond the annotations.

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?

Front-loaded with purpose, then page size, then returned fields, then pagination and slug sourcing. The field enumeration (title, link, thumbnail, views, likes, duration, source channel) is slightly long given an output schema exists, but it is one tight block with 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?

Covers what the tool returns at a glance, how to page, where to get valid slugs, and one important failure mode, which is more than adequate for a two-parameter read tool with an output schema. It stops short of describing ordering or whether an empty category returns an empty list.

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; the description earns a bump by restating the cursor continuation contract in workflow terms and warning that top-level category slugs fail. The slug format details (lowercase, URL accepted) remain only in the schema.

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 ('List the newest clips made in a Kick game or activity category') with scope defined as category-level rather than channel-level. It never names the immediate siblings kick_clips or kick_channel_clips, so the agent must infer the distinction from the word 'category'.

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?

Gives concrete prerequisites and a failure condition: get slugs from kick_subcategories, and top-level categories like 'games' return not found. It does not explicitly say when to prefer this over kick_clips or kick_channel_clips, which would complete the routing 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 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?