Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_channel_videos

Retrieve a Kick channel's recent past broadcasts (VODs) newest first, including titles, durations, views, and video links. Use it to review a channel's recent stream history.

Instructions

List a Kick channel's recent past broadcasts. Returns a Kick channel's recent past broadcasts (VODs), newest first: id, uuid, title, start time, duration in milliseconds, views, language, mature flag, tags, categories, thumbnail and the kick.com video link. Kick returns a fixed window of recent videos (26 at the time of writing) with no paging, so this call takes only the channel slug. Playable stream sources 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it states result ordering (newest first), the fixed 26-item window with no paging, that playable stream sources are never returned (a notable exclusion), and that an unknown channel returns not found. Missing auth/rate-limit details keeps it below a 5.

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 and information-dense—field enumeration, ordering, paging limit, and error case all arrive in a compact block. The opening two sentences repeat the same purpose ('List ... past broadcasts' then 'Returns ... past broadcasts'), a minor redundancy that costs it a point.

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 single-param, no-annotation, no-output-schema tool, the description covers everything an agent needs: what is returned (all fields listed), ordering, no-paging constraint, excluded data, and the not-found error. Nothing essential 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 the single slug parameter is already documented (case-insensitive, URL accepted) in the schema. The description restates that 'this call takes only the channel slug', adding confirmation but no new syntax or format detail beyond the schema. Baseline 3 applies.

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 a Kick channel's recent past broadcasts', clarifying these are VODs (with id, title, duration, etc.), which separates it from live-stream siblings like kick_channel_streams. It doesn't explicitly name a sibling to reroute to, but the 'past broadcasts (VODs)' framing makes the retrieval target clear.

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?

The description implies usage context (channel VOD listing, no paging, channel-slug-only) but never says when to choose this over alternatives such as kick_video or kick_channel_streams. There are no explicit when-to-use or when-not-to-use conditions; the agent must infer selection from the resource description alone.

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