Crawlora MCP

kick_livestreams

Read-only

List live broadcasts on Kick and return each stream's title, viewer count, start time, language, category, tags, thumbnail and channel. Use this to see what is live right now, filtered by language code (see kick_languages for common ones) or category id (from kick_subcategories), sorted by viewers or Kick's featured order; pass after with the previous next_cursor to page onward.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kick_livestreams"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Ordering: viewer_count_desc is most viewers first (default), featured is Kick's featured order. Documented values: viewer_count_desc, featured.
`after`	No	Previous response's next_cursor; omit for the first page
`limit`	No	Page size, 1 to 100; defaults to 24
`language`	No	Stream 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_id`	No	Category id from kick-subcategories' or kick-search-categories' own id field

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and an output schema exists, so the safety and return-shape burdens are covered elsewhere. The description still adds real behavior: pagination is cursor-based via a previous response's next_cursor, and results are ordered either by viewer count or Kick's featured ordering. It doesn't discuss freshness/latency of live data or rate limits, which keeps it below 5.

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?

Purpose and returned fields are front-loaded, then filtering/sorting, then pagination – a sensible order. The enumeration of return fields is somewhat wasted given an output schema exists, but the text is dense and free of filler.

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 5-optional-parameter read tool with full schema coverage, annotations and an output schema, the description covers filtering, ordering, and pagination adequately. The only meaningful gap is not distinguishing global live listing from per-channel stream listing among siblings.

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 the schema already defines sort values, the after cursor, the 1-100 limit, language code format, and category_id provenance. The description restates essentially the same facts (language/category lookups, viewer vs featured sort, after=past next_cursor) without adding syntax or format detail beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource ('List live broadcasts on Kick') and even enumerates the returned fields, so the agent knows exactly what comes back. It does not name or distinguish itself from the obvious sibling kick_channel_streams (live streams scoped to one channel), which is the one ambiguity an agent could hit.

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?

It states the use case clearly ('see what is live right now') and routes the agent to helper tools for the identifier parameters (kick_languages for language codes, kick_subcategories for category ids). It gives no exclusions or when-not guidance against alternatives like kick_channel_streams or kick_top_channels.

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?