Crawlora MCP

kick_channel_emotes

Read-only

List the chat emotes a Kick channel offers: its own custom emotes with id, name, subscribers-only flag and image link, plus the Global and Emoji sets every channel shares. Use this to see how big a streamer's emote library is or to resolve an emote name to an image; a channel with no custom emotes returns an empty channel set.

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

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

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds real behavioral value by describing the response composition (channel set plus Global/Emoji sets) and the edge case that a channel with no custom emotes returns an empty channel set. It omits auth/rate-limit details, which keeps it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler; the resource and return composition come first, followed by concrete uses and the empty-set edge case. Every clause carries information.

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, annotations, and a fully documented parameter, the description covers everything an agent needs to select and invoke the tool, including the empty-result edge case. Only minor operational details (e.g., result caps) are absent.

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?

There is a single slug parameter with 100% schema coverage, including format notes (case-insensitive, URL accepted), so the schema does the heavy lifting. The description adds nothing about the parameter, which is the expected baseline 3 for high coverage.

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 enumerates the returned fields (id, name, subscribers-only flag, image link) plus the Global and Emoji sets. This clearly distinguishes it from the other kick_channel_* siblings, which cover channel info, clips, streams, and videos.

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?

Gives two concrete use cases ('see how big a streamer's emote library is' and 'resolve an emote name to an image'). No explicit when-not or named alternative is given, but no sibling meaningfully overlaps with emote listing, so the context is clear without exclusions.

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?