Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Check whether a Kick channel is live

kick_channel_livestream_get
Read-onlyIdempotent

Check whether a Kick channel is live and retrieve its stream details, including title, category, viewer count, language, tags, and timing. Provide the channel slug to get current status.

Instructions

Check whether a Kick channel is live, with its title, category, viewers, language, tags and the stream record's timing. 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_livestream_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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value by enumerating the returned fields, which is important since no output schema exists. It does not say what happens when the channel is offline (an error versus a false/live flag), which is the defining behavioral question for a liveness check.

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 well-formed sentence with the return payload front-loaded and no wasted clauses. The trailing 'Requires `slug`' is slightly redundant with the schema's required list but is brief enough to be harmless.

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?

For a simple read-only single-parameter check with annotations and no output schema, the description mostly suffices by naming the return fields. The notable gap is the offline case and any rate or auth behavior, neither of which is covered anywhere in the structured data.

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%, and the slug field's casing and hyphen/underscore conventions are documented in exhaustive detail in the schema itself. The description only echoes 'Requires `slug`' and adds no meaning about the context, llm_model or conversation_id parameters. Baseline 3 applies when the schema carries the parameter semantics.

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 and resource ('Check whether a Kick channel is live') and enumerates the payload the check returns (title, category, viewers, language, tags, timing). It is distinguishable from kick_channel_get, which reads channel metadata rather than liveness. It never names a sibling or the boundary explicitly, which keeps it from a 5.

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 restates the required field rather than saying when to use this tool. Nothing tells the agent when to prefer this over kick_channel_get or tiktok_profile_live_check, and no when-not condition or precondition is given.

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