Skip to main content
Glama

Rank clipping campaigns by pay per clip

rank_campaigns
Read-onlyIdempotent

Live clipping campaigns (people paying for Shorts/TikTok/Reels clips of streams) ranked by what a typical approved clip has actually earned, with rate per 1,000 views, cap per clip, budget left and days of budget left. Use for 'which GTA 6 clipping campaign pays most', 'best clipping campaigns right now'. Data refreshes every 30 minutes.

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": "rank_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (default 10)
filterNogta = GTA campaigns only; gaming = gaming and streamer campaigns (default); all = every campaign
platformNoOnly campaigns that pay on this platform

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the ranking metric (actual earnings of a typical approved clip, not advertised rates) and the 30-minute data freshness, both of which materially affect how an agent interprets results. It doesn't mention pagination behaviour for the `limit` cap or ordering ties, leaving a small 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?

It is front-loaded with the resource and ranking basis, then use cases, then freshness — a sensible order. The opening sentence carries a long list of returned metrics that could be trimmed, but each item is informative rather than filler.

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 usefully enumerates the returned metrics and the freshness cadence that a ranking tool needs. Combined with 100% parameter coverage, an agent has enough to call and interpret it. Only minor gaps remain around ordering stability and how many results the ranking can draw from.

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 description coverage is 100%, so the parameters and their enum meaning are already fully documented, establishing a baseline of 3. The description reinforces the GTA framing through its example query but adds no syntax, default, or interaction detail (e.g. how `filter` and `platform` combine) beyond what the schema states.

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 — ranking live clipping campaigns — and states the exact ranking basis ('what a typical approved clip has actually earned'), plus the fields returned (rate per 1,000 views, cap per clip, budget left, days of budget left). This is clearly distinct from `campaign_details`, which by name would return a single campaign's detail; an agent can choose between them without opening a schema.

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 gives concrete triggering questions ('which GTA 6 clipping campaign pays most', 'best clipping campaigns right now'), which is real when-to-use guidance rather than implied usage. It stops short of explicit exclusions — e.g. it never says to use `campaign_details` for a specific campaign — so it misses the top band.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.