Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_video

Retrieve a Kick.com past broadcast's public metadata by video UUID or URL without needing the channel, including title, timing, status, views, and owner.

Instructions

Get a Kick video by its uuid. Returns one Kick (kick.com) past broadcast looked up by its recording's uuid, without needing the channel: uuid, title, start time, duration in milliseconds, the viewer count Kick reports, views, status, language, mature flag, tags, categories, thumbnail, the owning channel and the kick.com video link. id is the uuid from kick-channel-videos or kick-channel-streams, or a kick.com video URL. Only public data is read and no playable media is returned. An unknown video returns not found.

Input Schema

NameRequiredDescriptionDefault
idYesVideo uuid (36 characters) from kick-channel-videos or kick-channel-streams, or a kick.com video URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares 'Only public data is read', clarifies that 'no playable media is returned' (important for a video tool that might be mistaken for a downloader), and specifies the unknown-id behavior as not found. Missing only auth/rate-limit context, which is minor for a public read.

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 scope are front-loaded in the first two sentences, with caveats at the end. The long field enumeration is justified because there is no output schema, though it reads as a run-on list rather than structured detail.

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 one-parameter read tool with no annotations and no output schema, the description covers identification, source of the id, the full returned field set, the read-only/no-media constraint, and the not-found case. An agent has everything it needs to call this correctly.

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% and the parameter's schema text already says 'Video uuid (36 characters) from kick-channel-videos or kick-channel-streams, or a kick.com video URL'. The description restates essentially the same fact, so it adds little beyond the schema; baseline 3 applies.

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 ('Get a Kick video by its uuid') and immediately scopes it: a past broadcast from kick.com looked up by recording uuid, without needing the channel. That distinguishes it from listing siblings like kick_channel_videos and from clip tools without the agent needing to open any schema.

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 tells the agent where the id comes from ('the uuid from kick-channel-videos or kick-channel-streams, or a kick.com video URL'), which effectively documents the upstream workflow. It does not explicitly say when to prefer this over kick_clip or kick_clips, so no true exclusions are given.

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