Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Kick channel chatters

kick_channel_chatters_list
Read-onlyIdempotent

List up to 100 people in a live Kick channel chat, including moderators, VIPs, and total viewer count, to identify active participants and chat roles. Provide the channel slug.

Instructions

List up to 100 people in a live Kick channel's chat, with moderators, VIPs and the total count. 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_chatters_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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so safety is covered. The description adds genuinely non-obvious behavior: a hard cap of 100 entries and that the payload includes moderators, VIPs and a total count. It stops short of explaining pagination beyond 100 or behavior for offline channels.

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 the resource and its 100-item cap stated first. The trailing 'Returns a list.' is close to redundant with the opening verb and does not earn its place.

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?

With no output schema, the description carries the burden of describing return content; it mentions moderators, VIPs and a total count but gives no shape (e.g. per-user fields, ordering, whether the total is separate from the list). For a simple read-only list tool this is adequate but leaves gaps an agent must discover by calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already carries full parameter meaning, setting the baseline at 3. The description only repeats 'Requires `slug`', but since the schema is exhaustive, little description-side elaboration is needed.

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 names a specific verb and resource ('List ... people in a live Kick channel's chat') and adds scope detail (up to 100, moderators, VIPs, total count). It is clearly distinguishable from the sibling list tools, which cover clips, emotes, goals, videos etc., though it does not explicitly name a sibling to route against.

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?

'live Kick channel's chat' implies the channel must currently be live, which is an implicit usage condition rather than an explicit one. There is no statement of when to prefer this over siblings such as kick_channel_get, nor what happens when the channel is offline.

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