Crawlora MCP

kick_channel

Read-only

Get a Kick channel's public profile and return its username, bio, follower count, verification, social handles, recent categories and, when live, the current broadcast with title, viewers and start time. Use this with a channel slug (or kick.com link) to identify or size a streamer or check whether they are live now; an unknown channel returns not found and no playable stream URL is returned.

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

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?

Annotations only cover read-only and open-world; the description adds real behavioral context beyond them: fields are conditional ('when live, the current broadcast'), an unknown channel yields not found, and no playable stream URL is ever returned. That last point is a meaningful capability limit an agent would otherwise assume wrongly.

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 its field set, followed by usage. The first sentence is a dense comma-spliced enumeration that is slightly heavy but every element is substantive.

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?

Return values are carried by the output schema, so the description need only orient the agent, which it does by noting conditional live fields and the not-found case. Sufficient for a single-parameter read-only lookup; the missing piece is differentiation from the other kick_channel_* endpoints on the same slug.

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?

With 1 parameter at 100% schema coverage the schema already documents the slug, its case-insensitivity, and URL acceptance. The description's 'channel slug (or kick.com link)' merely restates the schema wording, adding no syntax or normalization detail beyond it.

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?

The description states a specific verb and resource ('Get a Kick channel's public profile') and enumerates exactly what the profile contains, so the agent knows the payload shape without opening the schema. It does not name or exclude any of the many overlapping siblings (kick_channel_streams, kick_channel_links, kick_search_channels), so the reader must infer why this aggregates social handles and live data while those exist separately.

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?

Explicit use cases are given: identify or size a streamer, or check whether they are live now, with the required channel slug/link form restated. There is no when-not guidance and no sibling alternative named, so an agent in an ambiguous case still has no routing rule.

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?