Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Kick channel emotes

kick_channel_emotes_list
Read-onlyIdempotent

Fetch a Kick channel's emotes plus shared global emotes and emoji using its slug, returning a list for chat display, moderation, or emote analysis.

Instructions

List a Kick channel's emotes plus the shared global emotes and emoji. Requires slug. Returns a list.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "kick_channel_emotes_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Kick channel slug, case-insensitive. Most replace the username's underscores with hyphens (e.g. `alfalfa-kid`, not `alfalfa_kid`), but some keep an underscore (e.g. `pala_okey`).
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description earns some credit for disclosing that global emotes and emoji are merged into the channel-specific results, which is genuinely non-obvious. It adds nothing about error behavior for a bad slug, pagination of the returned list, or ordering.

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?

Three short, front-loaded sentences with no filler; the scope disclosure comes before the requirement. The trailing "Returns a list" is close to dead weight since no output schema exists and it says nothing about the list's shape.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple read-only listing tool with full schema coverage and safety annotations supplied, so the bar is modest. Still, with no output schema, the description could have said more about the returned structure (e.g. the split between channel emotes and global emotes/emoji) instead of the near-empty "Returns a list."

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%, including a detailed slug-format note about underscores vs hyphens, so the schema does the heavy lifting. The description's "Requires `slug`" merely restates the schema and adds no new meaning for `context`, `llm_model`, or `conversation_id`. Baseline 3 is appropriate.

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 gives a specific verb and resource ("List a Kick channel's emotes") and adds scope detail that the name alone does not convey: the result also includes shared global emotes and emoji. It does not explicitly contrast with any sibling, but the resource is distinct enough among the channel-* listing tools that an agent can tell what it fetches.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only guidance is "Requires `slug`," which is a prerequisite already enforced by the schema's required array. There is no statement of when to choose this over another listing tool, no exclusion, and no note about what a caller gets if the channel has no custom emotes.

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