Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Kick clips

kick_clips_list
Read-onlyIdempotent

List Kick clips filtered by views, time window, or category; page through results with cursors.

Instructions

List Kick clips globally by views or date and time window, by category, or the newest clips across Kick; cursor paging. Optional inputs: category, sort, time and cursor. 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_clips_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo`view` (most viewed) or `date` (newest).
timeNoTime window.
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.
categoryNoKick category slug (e.g. `just-chatting`).
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 establish read-only, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds pagination semantics ('use cursor when paginated') and confirms the return is a list, but omits result limits, default ordering, and what an unfiltered call returns.

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 scope and modes, then the return/pagination note. Little waste, though the parameter enumeration partially duplicates the schema.

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 listing tool with a fully described schema and annotations covering the safety profile, the description covers filtering modes, paging, and return shape. Missing only edge-case behavior such as unfiltered defaults and result caps.

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 both enums are documented in-schema, so the baseline is 3. The description merely enumerates `category`, `sort`, `time`, and `cursor` without adding format or interaction details beyond what the schema already says.

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 Kick clips') and scopes the coverage explicitly as 'globally', which implicitly contrasts with the channel-scoped sibling. It stops short of naming `kick_channel_clips_list` directly, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It conveys the available modes (by views, by date/time window, by category, newest) which implies when each parameter applies, but it never states when to choose this tool over the channel-specific clips listing or how default behavior works with no filters. Usage is implied rather than guided.

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