Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_category_clips

Retrieve recent clips from a Kick game or activity category, returning one page at a time with a cursor for pagination.

Instructions

List the newest clips in a Kick category. Returns one page of 20 clips made in a Kick (kick.com) game or activity category, newest first: id, title, kick.com link, thumbnail, views, likes, duration in seconds, creation time, mature flag, category, the channel it came from, with a cursor for the next page. slug is a category slug from kick-subcategories such as just-chatting; a top-level category such as games has no clip page and returns not found. Only public data is read and no playable media is returned.

Input Schema

NameRequiredDescriptionDefault
slugYesCategory slug from kick-subcategories or kick-search-categories, lowercase; a kick.com/category URL is also accepted
cursorNoPrevious response's next_cursor; omit for the newest page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full load and does so well: page size of 20, newest-first ordering, cursor-based pagination, a stated failure mode (not found for top-level categories), public-data-only reads, and an explicit note that no playable media is returned. That is more behavioral context than most annotated tools provide.

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-loads the action and result in the first sentence, then constraints. The middle clause enumerating every returned field is long but earns its place because there is no output schema. Slight density rather than waste.

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?

No output schema exists, and the description fully compensates by enumerating returned fields, describing pagination and ordering, and warning about the top-level-category failure case. An agent can call this correctly without inspecting anything else.

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 real meaning: slug must be a subcategory slug rather than a top-level one, ties it to kick-subcategories, and explains the cursor as the previous response's next_cursor. It stops short of showing slug format examples beyond one lowercase hyphenated name.

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?

States a specific verb and resource ("List the newest clips in a Kick category") and scopes it to a category, which separates it from channel-level or global clip siblings. The required slug is named, so an agent knows exactly what identifies the target.

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 a concrete when-not rule: top-level categories like "games" have no clip page and return not found, and slugs should come from kick-subcategories (e.g. just-chatting). It never names a sibling alternative (e.g. kick_channel_clips) for channel-scoped clips, so selection against siblings is still partly inferred.

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