Crawlora MCP

kick_channel_videos

Read-only

List a Kick channel's recent past broadcasts and return each video's title, start time, duration, views, language, categories, thumbnail and kick.com link, newest first. Use this to review a streamer's recent output or content mix after identifying the channel; Kick returns a fixed recent window with no paging and no playable stream URL.

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_channel_videos"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Channel slug from kick.com/{slug}, case-insensitive; a kick.com URL is also accepted

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

A3.9/5.0

Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses the important behavioral limits: a fixed recent window, no pagination, no playable stream URL, and newest-first ordering. That is real context an agent cannot get from the annotations, though it says nothing about error behavior for invalid slugs.

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?

Two sentences, front-loaded with the resource and the returned fields before the usage hint. The field enumeration is long but serves the reader deciding whether this tool yields what they need; little is wasted.

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?

With an output schema present and annotations covering read-only/open-world safety, the description need only add the window, ordering, and pagination constraint—all of which it does. An agent has enough to call this correctly, with only failure modes left unstated.

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 description coverage is 100% and the single slug parameter documents case-insensitivity and URL acceptance, so the schema carries the load. The description only implies the input via 'after identifying the channel', adding no format or edge-case 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') plus the exact fields returned, so its scope is unambiguous. It implicitly separates itself from kick_video and clip tools by noting there is no playable stream URL, but never names a sibling explicitly.

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?

'Use this to review a streamer's recent output or content mix after identifying the channel' gives a clear triggering context, and 'no paging and no playable stream URL' functions as a when-not for playback or pagination-seeking use cases. It stops short of naming alternatives such as kick_video or kick_channel_streams.

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?