Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

kick_channel_links

Lists a Kick channel's link and text panels under its stream, including titles, descriptions, URLs, and images, using the channel slug or a kick.com URL.

Instructions

List a Kick channel's link panels. Returns the panels a Kick (kick.com) channel shows under its stream, in the order Kick shows them: link panels (tip pages, merch, social profiles) with title, description, URL and image, and text panels (FAQ, rules, disclaimers) that are only a title and description. slug is the channel slug from its kick.com address, case-insensitive; a full kick.com URL is also accepted. Only public data is read and no playable media is returned. An unknown channel returns not found.

Input Schema

NameRequiredDescriptionDefault
slugYesChannel slug from kick.com/{slug}, case-insensitive; a kick.com URL is also accepted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/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 discloses ordering semantics, the two panel variants, that only public data is read, that no playable media is returned, and that an unknown channel returns not found. It could still say more about pagination or response envelope, but the behavioral picture is unusually complete.

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?

One dense but well-ordered paragraph that leads with the action and the return shape, then the parameter, then the safety/error notes. Slightly duplicative of the schema on the slug clause, but no wasted framing.

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?

There is no output schema, so the description must explain returns, and it does: link panels carry title, description, URL and image while text panels carry only title and description. Error and data-privacy behavior are also covered; only pagination/volume limits are unaddressed.

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 schema description already states the slug is case-insensitive and accepts a kick.com URL; the description repeats this almost verbatim, 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 ("List a Kick channel's link panels") and immediately clarifies what those panels are, which cleanly separates it from siblings like kick_channel, kick_channel_clips or kick_channel_streams.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The purpose implies when to use it, but there is no explicit routing: nothing says to prefer this over kick_channel or the other kick_channel_* tools when looking for channel info. Usage is inferable rather than stated.

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