Crawlora MCP

kick_search_channels

Read-only

Search Kick channels by name and return each match's slug, username, follower count, live flag, verification and link, most relevant first. Use this to find a streamer's slug before calling kick_channel, or set live=true to find who is broadcasting now; no matches returns an empty 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>"
    },
    "name": "kick_search_channels"
  }
}

Input Schema

Name	Required	Description
`live`	No	Only channels live now
`limit`	No	Maximum results, 1 to 100; defaults to 10
`query`	Yes	Channel name to search for, up to 100 characters

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond them: results come back most-relevant-first and a no-match query returns an empty list rather than an error. It does not discuss rate limits or pagination beyond the limit param.

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 sentences, zero filler, with the core capability and returned fields front-loaded before the routing advice and the empty-result caveat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be documented further; the description nonetheless sketches them briefly. Combined with read-only annotations, the empty-result behavior and the follow-up path to kick_channel, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameter documentation is already complete and a baseline of 3 applies. The description still adds value by framing the live flag as a scenario ('find who is broadcasting now') rather than just restating the schema's 'Only channels live now'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (search Kick channels by name) plus the exact fields returned and ordering. It also distinguishes itself from kick_channel by positioning this tool as the lookup step that precedes a detail fetch.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Two concrete usage paths are given: resolve a streamer's slug before calling kick_channel, or set live=true to find current broadcasters. The alternative kick_channel is named explicitly, but there is no when-not guidance (e.g. versus kick_livestreams or kick_top_channels for browsing).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?