Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_clip

Fetch a single Kick clip by ID to get its title, link, thumbnail, views, duration, start time, category, channel, and mature flag.

Instructions

Get one Kick clip. Returns one Kick clip by id: title, kick.com link, thumbnail, views, duration, creation time, the moment it starts inside the source broadcast, mature flag, category and channel. id is a clip id such as clip_01M5SKVA6GGAAAT5YPJ7J43WE4, from the id field of kick-channel-clips or kick-clips. A malformed id returns a 400 and an unknown clip returns not found. Playable clip URLs are never returned.

Input Schema

NameRequiredDescriptionDefault
idYesClip id from kick-clips' or kick-channel-clips' own clips[].id field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it documents error behavior (400 on malformed id, not found on unknown id) and a non-obvious output limitation ("Playable clip URLs are never returned"). It says nothing about auth, rate limits, or caching, so it is strong but not exhaustive.

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 is front-loaded in the first sentence and the field list is dense but purposeful; the error and no-playable-URL caveats follow logically. Slightly long enumeration of return fields keeps it from being maximally tight, but nothing is wasted 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?

For a single-parameter lookup with no output schema and no annotations, the description covers what is returned, how to obtain a valid id, and how failures manifest. An agent has everything needed to call it correctly and interpret results.

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 value beyond the schema by giving a concrete id format example (clip_01M5SKVA6GGAAAT5YPJ7J43WE4) and reiterating provenance from the two listing tools. That extra format guidance is genuinely useful for constructing valid calls.

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?

"Get one Kick clip" names a specific verb and resource, and the description immediately distinguishes it from siblings by naming kick-clips and kick-channel-clips as the sources of ids. The enumerated return fields (title, thumbnail, views, duration, start offset, mature flag, category, channel) make the scope unambiguous.

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?

The description routes the agent to the right prerequisite tools by stating the id "is a clip id ... from the id field of kick-channel-clips or kick-clips", which implies listing tools must be called first. It does not explicitly state when NOT to use this tool or name a competing detail endpoint, so it stops short of full when/when-not guidance.

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