Crawlora MCP

kick_video

Read-only

Get one Kick past broadcast by its recording's uuid and return its title, start time, duration, reported viewer count, views, status, language, categories, thumbnail, owning channel and link. Use this to resolve a video uuid or URL to its channel; get uuids from kick_channel_videos or kick_channel_streams. An unknown uuid returns not found.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Video uuid (36 characters) from kick-channel-videos or kick-channel-streams, or a kick.com video URL

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

Behavior4/5

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

Annotations already cover the safe/read-only profile, and the description adds real value beyond them: it discloses the not-found behavior for unknown uuids and notes the parameter accepts a kick.com URL as well as a raw uuid. It does not cover pagination or latency, but those are minor for a single-item lookup.

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?

Three sentences, front-loaded with the core action, then the routing guidance, then the error case. The enumerated return-field list partially duplicates what the output schema already provides, slightly diluting an otherwise tight description.

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?

With annotations and an output schema both present, the description covers input provenance, the resolution use case, and failure behavior. Only marginally incomplete in not clarifying clips-versus-broadcasts boundaries, which is largely handled by sibling naming.

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 coverage is 100% and the parameter's own description already specifies the 36-character uuid format and URL alternative, so the description adds no new syntax or constraint information. Baseline 3 applies when the schema carries the parameter semantics.

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 one Kick past broadcast by its recording's uuid') and immediately distinguishes itself from related siblings by naming kick_channel_videos and kick_channel_streams as uuid sources. An agent can separate this from kick_clip and kick_channel_videos without opening a 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 states the use case ('resolve a video uuid or URL to its channel') and tells the agent where to obtain the required id ('get uuids from kick_channel_videos or kick_channel_streams'). Nothing about when to reach for this tool versus its siblings 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.

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?