Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

kick_clip

Read-only

Get one Kick clip by id and return its title, link, thumbnail, views, duration, creation time, category, channel and where it starts in the source broadcast. Use this when you already have a clip id from kick_clips or kick_channel_clips; a malformed id is rejected and an unknown clip returns not found. No playable URL is returned.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declared, the description adds useful behavioral context: malformed ids are rejected, unknown clips return not found, and no playable URL is returned. It does not cover rate limits, authentication, or return-shape details, but the output schema covers the latter.

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?

Two compact sentences front-load what is returned and immediately follow with when to use it. Every clause carries distinct information: return fields, upstream id source, error behavior, and the no-playable-URL caveat.

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 an output schema and safety annotations, the description covers the remaining gaps: provenance of the id, error conditions, and the notable absence of a playable URL. Nothing an agent needs in order to call it correctly is missing.

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 id field already documents that it comes from kick-clips' or kick-channel-clips' clips[].id field. The description repeats this guidance but adds the malformed-id constraint rather than new syntax or format details, so it is adequate but not richer than the schema.

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?

The description names a specific verb and resource ('Get one Kick clip by id') and enumerates the returned fields, so an agent can distinguish it from feed tools like kick_clips or kick_channel_clips. It also scopes the lookup to a single clip and notes the absence of a playable URL, which further separates it from playback-oriented siblings like kick_video.

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?

It explicitly states the condition for use ('when you already have a clip id from kick_clips or kick_channel_clips'), naming the upstream tools that supply the required identifier. It also documents two relevant outcomes - malformed id rejection and not-found for unknown clips - giving the agent clear expectations for invoking it correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
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