Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List live Kick streams

kick_livestreams_list
Read-onlyIdempotent

List live Kick streams by viewers or featured, filtered by language, category, or group, with cursor pagination.

Instructions

List the live Kick directory with sort, language, category, group and cursor filters. Optional inputs: sort, language, categoryId, groupId, limit and 1 more. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
sortNo`viewers` (most watched) or `featured`. Default: `viewers`.
limitNoRows per page, 1 to 100. Default: 100.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
groupIdNoDirectory group id, 1 to 2147483647.
languageNoLanguage code (e.g. `en`, `es`, `ja`).
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.
categoryIdNoCategory id, 1 to 2147483647.
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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds pagination behavior ('use cursor when paginated'), which is useful, but says nothing about result volume, rate limits, or the fresh-response conversation_id sequencing the schema hints at.

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?

Two sentences, front-loaded with the resource and filters, with the pagination hint at the end. The phrase 'and 1 more' after listing six of nine parameters is vague filler that could be dropped.

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 9 parameters, two of them required meta-parameters (context, llm_model) plus a sequencing constraint on conversation_id, the description covers the data-surface adequately but omits nothing critical only because the schema documents those fields thoroughly. For a tool whose call protocol includes a non-parallel-call constraint, the description is on the thin side.

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 defaults, ranges and enum values are fully documented in the schema. The description only restates the filter names and an unhelpful 'and 1 more' count, adding no syntax or semantics beyond the structured fields.

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?

Description opens with a specific verb and resource: 'List the live Kick directory', and enumerates the filter axes (sort, language, category, group, cursor). That distinguishes it from channel-scoped siblings like kick_channel_livestream_get or kick_search, though no sibling is named explicitly.

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?

There is no when-to-use or when-not-to-use guidance. Nothing tells the agent how this directory listing differs in purpose from kick_categories_list or kick_channels_top_list, so selection must be inferred from names alone.

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