Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Kick channel clips

kick_channel_clips_list
Read-onlyIdempotent

List a Kick channel's clips filtered by views or date and time window; use a cursor to paginate through additional results.

Instructions

List a Kick channel's clips filtered by views or date and by time window, with a cursor. Requires slug. 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": {
      "slug": "<slug>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "kick_channel_clips_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`).
sortNo`view` (most viewed) or `date` (newest). Default: `view`.
timeNoTime window. Default: `all`.
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.
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, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds only that it 'Returns a list' and that the cursor should be used when paginated — genuine but thin extra context. It says nothing about page size, empty-result behavior, or whether a nonexistent slug errors or returns an empty list.

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 short sentences, front-loaded with the operation and its filters, then the requirement and return shape; nothing is padded. The only near-waste is 'Requires `slug`', which duplicates the schema's required list, though it is a useful early warning.

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 7-parameter read tool with no output schema, the description covers the essentials — scope, filters, cursor, and that a list is returned — while annotations cover safety. It leaves out meaningful details an agent would want, such as whether an invalid or nonexistent slug errors versus returns empty, and whether the cursor page size is fixed.

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 documents slug format/normalization, the `sort` and `time` enums with defaults, cursor reuse constraints, and the analytics parameters. The description restates 'Requires slug', the sort axes, and the cursor without adding anything the schema does not already say, so the baseline of 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?

The description gives a specific verb and resource ('List a Kick channel's clips') plus the filter axes (views or date, time window) and the cursor mechanism, so the agent knows exactly what it retrieves. It scopes to a single channel, which implicitly distinguishes it from the global `kick_clips_list`, but it never names that sibling, so the differentiation is inferred rather than stated.

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/when-not guidance and no mention of alternatives such as `kick_clips_list` (all clips) or `kick_clip_get` (single clip). The only routing-adjacent statement is 'Requires `slug`', which is a parameter constraint already enforced by the schema, not a usage condition.

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