Skip to main content
Glama

Estimate Twitch earnings

estimate_twitch_earnings
Read-onlyIdempotent

Estimate a Twitch streamer's monthly and yearly income from paid subs (tiers 1–3), Prime subs, Bits and ads, using the same formula as the TwitchBoard sub calculator. Defaults use US prices ($5.99 / $9.99 / $24.99), a 50% sub split, $2.50 per Prime sub, $0.01 per Bit and a $3.50 ad CPM. These are estimates; actual payouts vary by country, contract and ad fill.

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

Input Schema

NameRequiredDescriptionDefault
ad_cpmNoStreamer ad revenue per 1,000 ad impressions, in USD.
prime_subsNo
tier1_subsNo
tier2_subsNo
tier3_subsNo
avg_viewersNoAverage concurrent viewers, used for ad revenue.
tier1_priceNo
tier2_priceNo
tier3_priceNo
prime_payoutNo
revenue_splitNoStreamer share of sub revenue: 0.5 standard, 0.7 Partner Plus.
bits_per_monthNo
hours_per_monthNoHours streamed per month, used for ad revenue.
ad_minutes_per_hourNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: the baseline pricing assumptions, the 50% default split with a Partner Plus option mentioned in the schema, and the caveat that actual payouts vary by country, contract and ad fill.

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?

Three tight sentences: purpose and inputs first, defaults second, caveat last. The assumptions are front-loaded so an agent can decide quickly whether to override them, and no sentence is 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?

For a 14-parameter, zero-required estimation tool with no output schema, the description covers what is computed (monthly and yearly income), the default assumptions, and the accuracy caveat. A few inputs such as hours streamed and ad minutes per hour are left to the schema, but overall an agent has enough to call it correctly.

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 14 parameters and only 29% schema description coverage, the schema leaves much undocumented, and the description partially compensates by pinning the defaults ($5.99/$9.99/$24.99, 50% split, $2.50 Prime, $0.01 per Bit, $3.50 CPM). It says nothing about hours_per_month, ad_minutes_per_hour, avg_viewers or bits_per_month, so several inputs remain semantically thin.

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: estimate a Twitch streamer's monthly and yearly income, and enumerates the revenue sources (tier 1-3 subs, Prime, Bits, ads). The platform specificity ('Twitch') clearly distinguishes it from siblings like estimate_kick_earnings and estimate_tiktok_earnings.

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 platform name implies when to choose this over the Kick/TikTok estimators, and the note about the TwitchBoard formula gives context. However, there is no explicit when-to-use or when-not-to-use guidance, nor any statement that this is a modeling tool rather than a lookup of real payout data.

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.

Resources