Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

kick_languages

Retrieve the live list of Kick stream languages with codes and display names, enabling accurate language filtering for Kick livestream queries.

Instructions

List Kick stream languages. Returns the stream languages Kick shows in its own language picker, each with its code and display name (67 at the time of writing). These codes are all accepted by the language parameter of kick-livestreams, which also accepts further ISO-style codes the picker does not list. The list is read live from Kick, so it follows any language Kick adds.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and discloses that the list is read live from Kick, follows language additions, and contains 67 entries at the time of writing. It also explains compatibility with kick-livestreams, though it does not discuss authentication or rate limits.

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?

The description is front-loaded with the core action and then adds only relevant details about return shape, count, compatibility, and live sourcing. Every sentence contributes useful information without unnecessary verbosity.

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?

Given the tool has no parameters and no output schema, the description supplies enough context to call it correctly: it explains the resource, the returned fields, the approximate count, live-data behavior, and how the codes relate to kick-livestreams. Nothing critical is missing for such a simple list endpoint.

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?

The tool has zero parameters, so the baseline is 4 under the rubric. The description adds useful output context by stating that each returned language includes a code and display name, but there are no parameters whose semantics need further explanation.

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 uses a specific verb and resource: 'List Kick stream languages.' It also explains that the result is Kick's own language picker list with code and display name, making the tool's purpose concrete and distinguishable from broader Kick endpoint tools.

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?

It clearly links the returned codes to the language parameter of kick-livestreams, implying this tool should be used to obtain valid filter values. It also notes that kick-livestreams accepts additional ISO-style codes not shown by this picker, which usefully prevents over-reliance on the list, though it does not explicitly state when not to use this tool.

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