Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_clips

List Kick's site-wide clips as one page of 20, ordered newest first or ranked by views within a day, week, month or all-time window. Paginate with the returned next_cursor.

Instructions

List Kick's site-wide clips. Returns one page of 20 clips from across all of Kick, either newest first (sort=date, the default) or ranked by views inside a time window (sort=views with time=day, week, month or all). Each clip has its id, title, kick.com link, thumbnail, views, duration, category and channel. Page onward by passing the previous response's next_cursor as cursor. Playable clip URLs are never returned. Use kick-channel-clips for one channel's clips.

Input Schema

NameRequiredDescriptionDefault
sortNoOrdering: date is newest first (default), views ranks by views inside the time window
timeNoWindow that views ranks within; omit for Kick's default window
cursorNoPrevious response's next_cursor; omit for the first page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden; it discloses page size (20), default ordering, and the non-obvious negative constraint that playable clip URLs are never returned. It does not mention auth, rate limits, or whether the ranking window resets, which keeps it short of a 5.

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?

Four sentences, each doing distinct work: scope, ordering modes, returned fields, pagination, plus the sibling routing at the end. The most decision-relevant facts (site-wide, default ordering) are front-loaded with zero filler.

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 and no annotations, the description still enumerates the per-clip fields (id, title, link, thumbnail, views, duration, category, channel) and explains continuation via cursor. Everything an agent needs to call it and interpret the response is present.

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 baseline would be 3, but the description adds real semantics beyond the schema: it names the default for sort (date, newest first), explains that views ranking is scoped inside the time window, and states that cursor comes from the previous response's next_cursor. That interaction between sort and time is the subtle part and it is spelled out.

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 ('List Kick's site-wide clips') and immediately scopes it as site-wide rather than per-channel, which is the key distinction from kick-channel-clips. An agent can tell exactly what this returns without opening the schema.

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?

Explicitly names the alternative ('Use kick-channel-clips for one channel's clips') and lays out the two ordering modes with their preconditions (sort=views requires a time window). Covers the default and the paging workflow, so nothing is left to inference.

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