Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Kick top gifted streams

kick_livestreams_top_gifted
Read-onlyIdempotent

Lists live Kick streams ranked by gifts received, including channel, category, and viewer count, to help identify top-gifted broadcasts.

Instructions

List the live Kick streams receiving the most gifts, with their channel, category and viewer count. 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_livestreams_top_gifted"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.5/5.0
Behavior3/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, idempotentHint=true) and open-world scope, so the description's marginal burden is low. It does add what the payload contains (channel, category, viewer count) and confirms list output, which annotations do not provide, but says nothing about result count, pagination, or freshness beyond "live".

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 key verb and scope; nothing is padded. The trailing "Returns a list." is mildly redundant with the leading "List" but cheaply confirms output shape given there is no output 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 simple read-only listing tool with full annotation coverage, the description supplies purpose, ranking criterion, and return fields. Missing only minor details an agent might want, such as how many streams are returned or whether a count/period parameter exists.

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 the three parameters (context, llm_model, conversation_id) are meta/plumbing rather than tool-specific filters, so the schema carries the semantics. The description adds nothing about them, which is acceptable at high coverage, but also nothing about whether filtering or paging options exist.

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?

Specific verb and resource: "List the live Kick streams receiving the most gifts," with the ranking dimension (gifts) making it clearly distinct from kick_livestreams_list or kick_channels_top_list. It does not explicitly name a sibling to redirect to, which keeps it short of a 5.

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 implicit in the wording: an agent can infer it is for when the user wants top-gifted live Kick content. There is no explicit when-to-use, when-not-to-use, or alternative-tool routing guidance.

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