Crawlora MCP

kick_clips

Read-only

List Kick's site-wide clips, 20 per page, and return each clip's title, link, thumbnail, views, duration, category and channel. Use sort=views with time=day, week, month or all to find the most-watched recent clips, or sort=date for the newest; pass cursor with the previous next_cursor to page onward. Use kick_channel_clips for a single channel.

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_clips"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Ordering: date is newest first (default), views ranks by views inside the time window. Documented values: date, views.
`time`	No	Window that views ranks within; omit for Kick's default window. Documented values: day, week, month, all.
`cursor`	No	Previous response's next_cursor; omit for the first page

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.6/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: fixed page size of 20 and the cursor/next_cursor pagination loop, which an agent must know to page correctly. It does not mention rate limits or whether the listing is public/unauthenticated, but readOnlyHint and openWorldHint already cover the safety profile.

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?

Front-loaded with scope and page size, then routing, then pagination — a sensible order with no filler. The enumeration of returned fields (title, link, thumbnail, views, duration, category, channel) is somewhat redundant given an output schema exists, which slightly dilutes density.

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 annotations covering safety, 100% schema coverage, and an output schema handling return shape, the description supplies everything else an agent needs: page size, sort/time pairing, pagination mechanics, and sibling disambiguation.

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 would be 3, but the description goes further by explaining the interaction between sort=views and time (views ranks within the window) and how cursor consumes the previous response's next_cursor. That coupling is more than the schema states field-by-field.

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 with scope ('List Kick's site-wide clips, 20 per page') and enumerates the returned fields, so an agent knows exactly what comes back. It also names the sibling it is not ('Use kick_channel_clips for a single channel'), cleanly separating site-wide from per-channel listing.

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

Usage Guidelines5/5

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

Gives concrete when-to-use branches: sort=views combined with time=day/week/month/all for most-watched recent clips, sort=date for newest, cursor with next_cursor to continue paging. The alternative for per-channel clips is named explicitly, leaving nothing to inference.

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?