Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_channel_chatroom

Retrieve a Kick channel's chat restrictions and rules, including slow mode, subscriber/follower-only settings, emote-only mode, minimum account age, gifts, and the channel's rules text.

Instructions

Get a Kick channel's chat settings and rules. Returns a Kick (kick.com) channel's chat restrictions and rules: slow mode (delay between messages), subscribers-only, followers-only (minimum follow time), emotes-only and minimum account age, whether gifts are enabled, and the channel's chat rules text. slug is the channel slug from its kick.com address, case-insensitive; a full kick.com URL is also accepted. The pinned message is not returned. This call reads two Kick pages. 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/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses that the call reads two Kick pages (cost/latency), that the pinned message is excluded, and that an unknown channel returns not found (error behavior). It stops short of stating permission/auth requirements or response shape details beyond the field list.

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 purpose followed by a compact field enumeration, then scope caveats and error behavior. The long middle sentence earns its place by describing the return payload, though it is denser than strictly necessary.

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 a single required parameter, the description fully covers what an agent needs: where to get the slug, what fields come back, what is excluded, the read cost, and the not-found case.

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?

Only one parameter exists and schema description coverage is 100%; the schema already says the slug is case-insensitive and accepts a full kick.com URL. The description restates this same information verbatim, adding no new syntax or format guidance, so the 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's chat settings and rules') and then enumerates the returned fields (slow mode, subscribers-only, followers-only, emotes-only, minimum account age, gifts, rules text), which effectively separates it from sibling channel tools like kick_channel or kick_channel_emotes.

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 implied by the field enumeration and the note that the pinned message is not returned and that an unknown channel yields not found. However, there is no explicit statement of when to choose this over sibling tools such as kick_channel or kick_channel_links, so the agent must infer 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