Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Kick category

kick_category_get
Read-onlyIdempotent

Fetch a Kick category by slug to get its group, tags, viewers, and follower count for social media research.

Instructions

Get a Kick category by slug with its group, tags, viewers and follower count. 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_category_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired. Kick category slug (e.g. `just-chatting`).
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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so safety behavior is covered. The description's added value is the return-content summary (group, tags, viewers, follower count), but it says nothing about failure behavior for an unknown slug or how fresh the viewer/follower counts are.

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?

Two short sentences with the resource identified first, the key second, and the requirement last. Nothing is padding and nothing important is buried.

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 lookup with no output schema, naming the returned fields gives an agent enough to decide whether this tool answers the question. Only minor gaps remain: error behavior on a bad slug and whether counts are real-time.

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%, including a format example (`just-chatting`) and a regex pattern for slug, so the schema does the heavy lifting. The description only restates the slug requirement and adds no meaning about the context, llm_model, or conversation_id parameters.

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 ("Get a Kick category") plus the lookup key (by slug) and the payload contents (group, tags, viewers, follower count). That clearly separates it from list-style siblings like kick_categories_list or kick_categories_top, though no sibling is named explicitly.

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?

Only usage signal is the precondition "Requires `slug`," which implies this is a direct lookup used when a slug is already known. There is no explicit when-to-use/when-not guidance and no routing to kick_categories_list for browsing versus this tool for slug lookup.

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