Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kick_drops

List Kick Drops campaigns with rewards, watch thresholds, publishers, and participating channels; filter results by active, expired, or all status.

Instructions

List Kick Drops campaigns. Returns Kick (kick.com) Drops campaigns, publisher-sponsored rewards that viewers earn by watching, newest first: id, name, status, start and end time, campaign page, the rule (for example Watch to redeem), the publisher with its logo, the game or activity category, every reward with the watch threshold that earns it and its image, and the channels taking part. status is active (the default), expired or all. Only public campaign information is read; no account or progress data.

Input Schema

NameRequiredDescriptionDefault
statusNoWhich campaigns to return: active (default), expired or all

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 disclose meaningful traits: results are ordered newest first, the read is public, and no account or progress data is touched. It stops short of stating pagination, rate limits, or result volume, which would round this out for a list tool.

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 ordering are front-loaded in the first sentence, and the long field enumeration that follows is one dense colon-list rather than padding. It is longer than most definitions but each clause maps to a real returned field, so little waste remains.

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 enumerating returned fields (id, name, status, times, page, rule, publisher, category, rewards, channels) is genuinely necessary and is done. Combined with the single documented enum parameter, an agent has enough to call this correctly; only pagination/volume is 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 single enum parameter already documents its three values and default in the schema. The description restates 'status is active (the default), expired or all' without adding format or behavior detail beyond that.

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?

First sentence gives a specific verb and resource ('List Kick Drops campaigns'), and the second defines what a Drop is on Kick. It is distinguishable from the sibling kick_* tools (channel, clips, categories, livestreams) which cover different resources.

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?

Usage is implied by the read-only, public-data note and the status filter, but no sibling or alternative is named and no explicit 'use this when' condition is given. An agent must infer that this is the list endpoint for drop campaigns rather than being routed to it.

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