Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_channel_emotes

Retrieve a Kick channel's chat emote sets, including its custom emotes and shared Global and Emoji sets, by channel slug or kick.com URL.

Instructions

List the chat emotes a Kick channel offers. Returns the chat emote sets available in a Kick (kick.com) channel: the channel's own custom emotes (id, name, whether subscribers only, image link), plus the Global and Emoji sets that every channel shares. slug is the channel slug from its kick.com address, case-insensitive; a full kick.com URL is also accepted. A channel with no custom emotes returns an empty channel set. Only public data is read and no playable media is 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.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and mostly does: it discloses that only public data is read, that no playable media is returned, that a channel with no custom emotes yields an empty channel set, and that an unknown channel returns not found. Missing auth/rate-limit or pagination notes, which keeps it short of 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 with the purpose, then return contents, then parameter behavior, then edge cases. Every sentence carries information, with only the slug sentence being redundant against the schema.

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?

There is no output schema, so the description fills that gap by describing the shape of the returned emote sets and their fields (id, name, subscriber-only flag, image link) plus the empty and not-found cases. Complete enough for correct invocation; only multi-result/pagination behavior is unaddressed.

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 schema description already says 'Channel slug from kick.com/{slug}, case-insensitive; a kick.com URL is also accepted.' The description repeats that near-verbatim, so it adds no meaning beyond the structured field. 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 ('List the chat emotes a Kick channel offers') and immediately enumerates what is returned: the channel's custom emotes plus the Global and Emoji sets. An agent can distinguish this from kick_channel_clips, kick_channel_videos, and kick_channel_links without opening any schema.

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 resource scope (emotes for a given channel) but the description never says when to pick this over sibling channel tools or what alternative exists if the agent wants clips, links, or chatroom info. Acceptable for a narrowly-named tool, but no explicit routing or exclusions.

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