Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_channel

Fetch a Kick channel's public profile and live broadcast details—including viewers, title, categories, and socials—by channel slug or kick.com URL.

Instructions

Get a Kick channel profile and live state. Returns a Kick (kick.com) channel's public profile and, when it is live, its current broadcast: username, bio, verification and affiliate flags, follower count, linked social handles, profile and banner images, recent categories, and a live object with title, viewers, start time, language, tags and categories (omitted when the channel is offline). slug is the channel slug from its kick.com address, case-insensitive; a full kick.com URL is also accepted. Playable stream 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.2/5.0
Behavior4/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 it well: it discloses the conditional live object ("omitted when the channel is offline"), the not-found behavior for unknown channels, and the explicit exclusion of playable stream URLs. Missing only operational traits such as rate limits, auth requirements, or caching/cost characteristics.

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 with the one-line purpose, then the payload, then parameter and edge-case notes — a sensible ordering. The return-field enumeration is long but earns its place since no output schema exists; a single dense paragraph is a minor readability cost.

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?

With no output schema and no annotations, the description must supply return shape, offline behavior, parameter format, and error case — and it supplies all four. An agent has everything needed to call this correctly and interpret an empty live object.

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%, so the single slug parameter is already fully documented. The description's statement that slug is case-insensitive and accepts a full kick.com URL is useful but verbatim what the schema property description already says, so it adds no meaning beyond structured data. Baseline 3 applies.

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 ("Get a Kick channel profile and live state") and then enumerates exactly what that means: public profile fields plus a conditional live object. That enumeration cleanly separates it from sibling tools that fetch stream URLs, clips, videos, or search across channels.

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?

The lookup context is unambiguous and the negative constraint "Playable stream URLs are never returned" steers an agent away from using this as a stream-resolution tool, implicitly pointing at the stream-specific siblings. It stops short of naming a specific alternative tool to call instead, so it is clear context without full explicit routing.

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