Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

kick_drops

Read-only

List Kick Drops campaigns (publisher-sponsored rewards earned by watching), newest first, with each campaign's name, dates, publisher, game category, rewards with the watch thresholds and images, and the participating channels. status is active (default), expired or all. Use this to see which games and creators currently offer drops; no account or progress data is returned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

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

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.1/5.0
Behavior4/5

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

Annotations already cover readOnly and openWorld, and the description adds real behavioral context: results are ordered newest first and no account or progress data is returned, which sets expectations about scope and safety. It does not discuss pagination or result caps, which is a minor gap.

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?

Two sentences, front-loaded with the action and scope, followed by the use case and a limitation. The dense enumeration of returned fields is somewhat redundant since an output schema exists, but overall it is tight.

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?

For a simple, read-only listing tool with an output schema and a fully documented single parameter, the description covers purpose, scope, ordering, defaults, and what is excluded. Only edge details like pagination or result limits are absent.

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?

With one parameter and 100% schema description coverage, the schema already documents the status enum including the default. The description restates those values and confirms the default, adding only modest value beyond the structured field.

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 (List) and resource (Kick Drops campaigns), immediately defining what a drop is in parentheses. It is clearly distinct from the other kick_* sibling tools such as kick_livestreams or kick_top_channels, which cover streams and channels rather than campaigns.

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?

The sentence 'Use this to see which games and creators currently offer drops' gives a clear intended use case, and the default status of 'active' is stated. It does not explicitly name an alternative tool or a case when another tool would be better, but for a unique resource type the practical ambiguity is low.

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