Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_search_channels

Search Kick channels by name and optionally filter to live broadcasts, returning IDs, usernames, follower counts, verification status, live flags, and kick.com links.

Instructions

Search Kick channels. Searches Kick channels by name and returns each match's id, slug, username, follower count, live flag, verification and kick.com link, most relevant first. query is required and at most 100 characters. live=true restricts to channels that are broadcasting now. limit is 1 to 100 (default 10). A search with no matches returns an empty list.

Input Schema

NameRequiredDescriptionDefault
liveNoOnly channels live now
limitNoMaximum results, 1 to 100; defaults to 10
queryYesChannel name to search for, up to 100 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it discloses the ranking order ("most relevant first"), the exact result fields returned, and that no-match yields an empty list rather than an error. It stops short of stating the read-only/no-side-effect nature or any rate/pagination behavior.

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?

The purpose and return shape are front-loaded in the first sentence, and the remaining sentences each add a distinct constraint or edge case. Slight waste in the near-duplicate opening ("Search Kick channels. Searches Kick channels by name...").

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 3-parameter search tool with no annotations and no output schema, the description covers return fields, sort order, parameter bounds, and the empty-result case, which is enough to call it correctly. Only side-effect/auth framing is missing.

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 the schema already documents query, live, and limit. The description largely restates those constraints (required query, 100-char cap, limit 1-100 default 10, live=true meaning broadcasting now) rather than adding format or edge-case nuance beyond them.

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 uses a specific verb+resource ("Search Kick channels", "Searches Kick channels by name") and enumerates the returned fields, so the operation is unambiguous. It never names a sibling like kick_channel or kick_livestreams, so an agent must infer differentiation from the "by name" phrasing alone.

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?

"Searches Kick channels by name" plus the live-only filter gives a clear picture of when this tool applies. There are no explicit exclusions or pointer to an alternative (e.g. fetching a single known channel by slug), which would be needed for a 5.

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