Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Kick channels and categories

kick_search
Read-onlyIdempotent

Search Kick channels and categories by keyword to find relevant streams and discover content. Enter a query of at least three characters and receive a list of matching results.

Instructions

Search Kick channels and categories by a word of at least three characters. Requires query. 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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "kick_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRequired. Words to search for, at least 3 characters. Double quotes, semicolons, backslashes, ampersands and emoji are not accepted.
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety and idempotency profile is covered by structured data. The description adds little beyond "Returns a list" – it does not say whether results are ranked, paginated, or truncated, nor how many results come back. That is a modest contribution over the annotations, not a rich one.

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?

Three terse sentences: purpose first, then the hard constraint, then the return shape – well front-loaded with no filler. It is arguably under-sized for a search tool, but nothing written is wasted.

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 a fully documented 4-parameter schema and a complete annotation set, the definition is usable as-is. The gap is the result: with no output schema, "Returns a list" leaves the agent unaware of what a channel or category record contains or how many results to expect, which matters for a search endpoint.

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 all four parameters – including query constraints, context, llm_model, and conversation_id – are already documented in the schema with equal or greater detail. The description's only parameter statement (">= 3 characters", "Requires `query`") restates the schema rather than adding syntax, format, or behavioral meaning. 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 names a specific verb and resource ("Search Kick channels and categories") plus the search key ("by a word"), which is enough to distinguish a keyword search from a listing tool. It stops short of naming which sibling to prefer over kick_channels_top_list or kick_categories_list, so it is clear but not sibling-differentiating.

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?

"Search ... by a word of at least three characters" implies the keyword-search use case rather than browsing catalogs, and "Requires `query`" flags its mandatory input. There is no explicit statement of when to use this instead of the sibling list/top tools on the same platform, so the routing guidance is only implied.

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