Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Kick channel gifter leaderboard

kick_channel_leaderboard_get
Read-onlyIdempotent

Retrieve a Kick channel's top gifters for all time, last week, and last month by channel slug to compare supporter rankings.

Instructions

Get a Kick channel's top gifters for all time, last week and last month. 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_leaderboard_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

A3.6/5.0
Behavior3/5

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

The annotations already declare this as read-only, idempotent, open-world, and non-destructive. The description adds useful behavioral scope by saying the result covers three time windows, but it does not discuss return shape, limits, or error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tightly written sentences with the core purpose and time-window scope front-loaded, and no unnecessary wording.

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 simple read-only leaderboard lookup with rich schema descriptions and clear annotations, the description covers the essential purpose, required parameter, and output scope. It could say more about the leaderboard size or response shape, but that is a minor gap.

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 parameter meanings are already supplied. The description only repeats that `slug` is required and adds no extra syntax or format guidance beyond the schema.

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 states a specific verb and resource: get a Kick channel's top gifters, scoped to all time, last week, and last month. It is clear what the tool does, though it does not explicitly differentiate itself from sibling channel tools.

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?

The description implies usage by describing the leaderboard data and noting that `slug` is required, but it gives no explicit when-to-use or when-not-to-use guidance relative to alternatives like `kick_channel_get` or other leaderboard tools.

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