Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_channel_clips

Lists a Kick channel's clips, returning 20 newest per page with titles, links, views, likes, duration, category, and creator. Use cursor pagination for older clips.

Instructions

List a Kick channel's clips. Returns one page of 20 clips from a Kick channel, newest first: id, title, kick.com link, thumbnail, views, likes, duration in seconds, creation time, mature flag, category, the viewer who made the clip and the channel. Page onward by passing the previous response's next_cursor as cursor; next_cursor is empty on the last page. Playable clip URLs are never returned. An unknown channel returns not found.

Input Schema

NameRequiredDescriptionDefault
slugYesChannel slug from kick.com/{slug}, case-insensitive; a kick.com 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.3/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 burden and does so: page size (20), ordering (newest first), all returned fields, cursor-driven pagination with an empty next_cursor terminating the sequence, and an explicit negative disclosure that playable clip URLs are never returned. It also documents the not-found behavior for unknown channels.

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?

Front-loaded with the core action, then page mechanics, then field list, then the limitation and error case. Every sentence carries distinct information and none repeats the schema verbatim.

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, so listing the returned fields in prose is necessary and done. For a two-parameter read with no annotations, the description covers scope, pagination, response shape, limitations, and error behavior — nothing needed to call it correctly 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% and both parameter descriptions already explain slug formats and the cursor's source. The description adds only that next_cursor is empty on the last page, which is a minor increment over the schema — baseline 3 is appropriate.

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 scoped resource: list clips belonging to a single Kick channel. The word 'channel' scopes it against the obvious siblings kick_clips (global) and kick_category_clips, so an agent can tell them apart from the description alone.

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

Usage Guidelines3/5

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

Usage is only implied — the agent must infer that this tool is the right one when a channel slug is known and kick_clips/kick_category_clips are not. Pagination mechanics are explained well, but there is no explicit when-to-use / when-not-to-use or named alternative.

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