Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_livestreams

Fetch live Kick broadcasts with viewers, category, language, and channel details. Filter by category or language, sort by viewer count or featured, and page through results with a cursor.

Instructions

List live broadcasts on Kick. Returns one page of Kick's live-stream directory: title, viewer count, start time, language, mature flag, tags, category, thumbnail and the channel for each live broadcast. sort is viewer_count_desc (the default, most viewers first) or featured. language filters to one stream language by code (kick-languages lists the languages Kick shows in its own picker; the directory accepts a wider range of codes than that list, and an unrecognized code returns a 400), and category_id filters to one category by the numeric id from kick-subcategories or kick-search-categories. limit is 1 to 100 (default 24). Page onward by passing the previous response's next_cursor as after; next_cursor is empty on the last page.

Input Schema

NameRequiredDescriptionDefault
sortNoOrdering: viewer_count_desc is most viewers first (default), featured is Kick's featured order
afterNoPrevious response's next_cursor; omit for the first page
limitNoPage size, 1 to 100; defaults to 24
languageNoStream language code such as en, ja, es, pt-BR, optionally with a region (2 to 3 letters, then an optional 2 to 4 letter region); see kick-languages for the codes Kick lists
category_idNoCategory id from kick-subcategories' or kick-search-categories' own id field

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?

No annotations exist, so the description must carry the burden, and it does reasonably well: it discloses the default sort and page size, how to page forward, that next_cursor is empty on the last page, and that an unrecognized language code yields a 400. It doesn't address rate limits or what an empty directory means, but the core behavior is covered.

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?

A single dense paragraph that front-loads the purpose and returned fields before covering parameters and pagination. Every sentence carries information, though the returned-field enumeration is lengthy and could be trimmed.

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?

With no output schema, the description supplies the return shape itself by listing the fields per broadcast, and it covers filtering, ordering, page size and cursor paging. An agent has everything needed to call it correctly and know what comes back.

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 the baseline is 3, but the description adds real value beyond the schema by noting the directory accepts a wider range of language codes than kick-languages shows and that an unrecognized code returns a 400, plus naming both kick-subcategories and kick-search-categories as id sources.

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 ('List live broadcasts on Kick') and immediately clarifies it returns one page of Kick's live-stream directory, enumerating the returned fields. An agent can distinguish it from channel-scoped siblings like kick_channel_streams, 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?

Provides strong in-tool guidance on sort, language, category filters and pagination via next_cursor, but never states when to use this tool versus kick_search_channels, kick_top_channels or kick_channel_streams. Usage is implied rather than disambiguated against alternatives.

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