Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Kick events, or read one event

kick_events_list
Read-onlyIdempotent

List Kick events, featured events, or one event by ID or slug, and optionally fetch its live streams or clips for event discovery.

Instructions

List Kick events, the featured events, or one event by id or slug, its live streams or its clips. Optional inputs: event, include and featured. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
eventNoEvent ULID or slug (e.g. `nopixel-v`).
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
includeNoWhen `event` is given: return its live streams or its clips instead of the event record. Send `streams` or `clips`, not both.
featuredNoReturn the featured events instead of the browse list.
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.4/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 safety is covered. The description adds only 'Returns a list' plus a hint of the selectable modes, which is modest added context. It does not disclose anything about pagination, result caps, or how the shape differs across the four modes.

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?

The definition is a short, front-loaded statement of capability followed by the input options and return type. Nothing is padded, though the closing 'Returns a list' is redundant given the opening 'List ...' and adds little.

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 six parameters, four operational modes, and no output schema, the description should explain that return shape varies by mode (event record vs stream list vs clip list). It only says 'Returns a list', leaving a meaningful gap for a multi-mode read tool, though annotations cover the safety profile.

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 `event`, `include`, `featured`, `context`, `llm_model`, and `conversation_id` are all fully documented in the schema, including the mutual exclusivity of streams/clips. The description merely restates three of the optional inputs by name and adds no syntax or constraint detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 uses a specific verb and resource and enumerates its modes: list events, list featured events, fetch one event by id or slug, or return its streams/clips. This lets an agent distinguish the tool's capabilities internally. It does not, however, contrast against obvious siblings like kick_clips_list or kick_livestreams_list, which serve overlapping data.

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 tool lists or reads events, and the `event` vs `featured` inputs select the mode. There is no statement of when to pick this over the dedicated clips/livestream siblings, nor any when-not guidance or prerequisite call ordering.

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