Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List top Kick categories by viewers

kick_categories_top
Read-onlyIdempotent

Lists the busiest Kick categories with current viewer counts, banners, and groups, so you can identify high-traffic streams. Use the optional limit to cap rows from 1 to 100.

Instructions

List the busiest Kick categories with current viewers, banner and group. Optional inputs: limit. 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_categories_top"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows, 1 to 100.
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 the returned fields (current viewers, banner, group) and that the result is a list, but says nothing about ordering, result size, or the conversation_id handshake requirement that governs parallel calls.

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, front-loaded sentences with no padding. The 'Optional inputs: limit' and 'Returns a list' fragments carry little information and partly duplicate structured fields, but nothing is verbose.

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 no output schema, the description must carry return-value expectations, and it only lists three example fields without identifying fields such as category name or id. Given 100% schema coverage the parameter side is fine, so this is adequate but not complete.

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 coverage is 100%, so every parameter is documented in the schema. The description only echoes 'optional inputs: limit,' which repeats schema text and adds no meaning about default values or ranking behavior; 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?

States a specific verb and resource plus the distinguishing scope: 'busiest Kick categories with current viewers, banner and group.' An agent can tell this is a ranked category listing, though the description never explicitly contrasts it with the sibling kick_categories_list.

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?

No when-to-use or when-not-to-use guidance is given. The only alternative named is an implicit one in the tool name ('top' vs 'list'), and the definition leaves the agent to infer it rather than stating conditions or exclusions.

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