Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Kick channel

kick_channel_get
Read-onlyIdempotent

Retrieve a Kick channel's profile, social links, follower count, chat modes, subscriber badges, and live stream status by slug.

Instructions

Get a Kick channel's profile, socials, follower count, chat modes, links, subscriber badges and live stream. Requires slug.

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

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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing the payload contents, but says nothing about failure behavior for an unknown slug, rate limits, or whether the live-stream field is null when offline.

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?

One dense sentence front-loads the verb and resource, followed by a short requirement note. The trailing 'Requires `slug`' is redundant with both the schema's required list and its own parameter description, a minor waste.

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?

For a read-only fetch with no output schema, the description does the necessary work by listing the returned facets, which is what an agent needs to decide if one call suffices. Remaining gaps (offline/null handling, not-found behavior) are minor but real for an open-world lookup.

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%, so the schema already carries the slug format guidance, including the underscore-vs-hyphen caveat, and documents context/llm_model/conversation_id. The description only repeats the requirement for `slug`, adding no meaning beyond the schema; baseline 3 applies.

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?

States a specific verb ('Get') and resource ('Kick channel') and enumerates exactly what comes back: profile, socials, follower count, chat modes, links, subscriber badges, live stream. That enumeration implicitly distinguishes it as the aggregate channel-overview call versus siblings like kick_channel_emotes_list or kick_channel_goals_list, though no sibling is named.

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 only implied: the field list suggests this is the broad 'everything about a channel' call, useful as a first lookup. There is no explicit when-to-use, and no acknowledgment that 'live stream' overlaps with kick_channel_livestream_get, leaving the agent to infer the boundary.

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