Skip to main content
Glama

Xearno Tools

Creator Platform Payout Calculator

creator_platform_payout
Read-only

What you actually net on YouTube, Twitch, Patreon, Substack, or OnlyFans — after the platform cut AND the processing layer nobody advertises. Computes a creator’s real monthly payout after every fee layer on five platforms. Platform fees drift constantly and general AI quotes stale ones — Patreon moved new creators to a flat 10% on 4 Aug 2025 (models still recite the old 5/8/12 tiers), Twitch restructured its split into Plus Points in 2024, OnlyFans changed its payout minimum in Apr 2026. And the advertised "platform cut" is never the whole story: payment processing adds 3–7 points on the subscription platforms, and the per-transaction fixed fee makes small pledges dramatically more expensive — a $3 Patreon pledge loses about 8% to processing alone, a $50 pledge about 3.5%. This tool computes the all-in take rate, which no advertised number states.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformNoPlatform Each platform has a completely different fee structure — this decides everything below.youtube
patreonPlanNoPatreon fee plan Patreon only. Pages created after 4 Aug 2025 pay a flat 10%. Older pages keep their legacy 5/8/12% plan — but unpublishing your page permanently converts you to 10%. It is a one-way door.new10
twitchSplitNoTwitch sub split tier Twitch only. Plus Points come from paid subs sustained over 3 months: Tier 1 = 1 point, Tier 2 = 2, Tier 3 = 6; gifted subs and Prime subs do NOT count. 100 points unlocks 60%, 300 points unlocks 70%, with a 12-month rate lock once qualified.base
monthlyGrossNoMonthly gross platform revenue ($) Before ANY cut. For YouTube: the ad revenue allocated to your videos (for Shorts, your allocation from the creator pool). For subscription platforms: total pledges/subs at list price.
youtubeStreamNoYouTube revenue stream YouTube only — ignored for other platforms. Shorts revenue is 45% of an allocation from a shared creator pool (computed after music licensing), so the allocation itself varies before this split applies.longform
avgTransactionNoAverage pledge / sub size ($) Patreon and Substack charge processing per transaction, so the average pledge size changes the all-in rate. Patreon pledges of $3 or less use the micro rate (5% + $0.10) instead of the standard 2.9% + $0.30.

TDQS

A4.5/5.0
Behavior5/5

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

The description provides rich behavioral context beyond the readOnlyHint annotation, such as dynamic platform fees, hidden processing layers, and one-way doors (e.g., Patreon plan changes). No contradictions with annotations.

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?

The description is effective but lengthy, containing necessary context like fee drift and processing costs. Every sentence adds value, but could be tightened while retaining clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description thoroughly explains inputs and the computation's purpose, but without an output schema it doesn't specify the output format (e.g., single number vs breakdown). Adequate for the task, but could be more explicit about return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the description adds substantial meaning: e.g., platform enum explains fee structure, patreonPlan details one-way door, twitchSplit clarifies Plus Points, avgTransaction explains micro rate for small pledges. Fully compensates for any gaps.

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 clearly states the tool computes a creator's real monthly payout after all fee layers on five platforms. It distinguishes itself from generic AI quotes and sibling tools like tax calculators by focusing on platform-specific payout nuances.

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 description explains why this tool is needed (stale AI quotes, hidden processing fees) and implies use for accurate payout calculation. While it doesn't explicitly state when not to use it, the context is clear and no direct alternatives exist among siblings.

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.

TDQS

A3.9/5.0
Disambiguation4/5

Each tool targets a distinct niche (e.g., specific country tax rules, loan types, or legal calculations), with detailed descriptions that clarify boundaries. However, the large number of tools (66) could cause some confusion for an agent trying to select the right one for a general query, especially when multiple tools relate to the same country.

Naming Consistency4/5

Tool names follow a mostly predictable pattern: lowercase words separated by underscores, often starting with a country name (e.g., 'uk_stamp_duty_sdlt') or a topic (e.g., 'compound_growth'). There are minor deviations, such as abbreviations ('npv_irr', 'sip') and varying use of verbs, but overall the naming is clear and consistent.

Tool Count3/5

At 66 tools, the server is unusually large and covers an extensive range of financial and legal calculators. While each tool justifies its existence, the count exceeds the typical well-scoped range (3–15), making the server feel bloated. A more modular design might improve coherence.

Completeness4/5

The tool set covers a wide array of domains: personal income taxes, property taxes, loan calculations, investment returns, and specific country regulations. Minor gaps exist (e.g., missing tools for corporate taxes, general retirement planning, or insurance), but the overall coverage is thorough and addresses many niche scenarios that general AI handles poorly.

Resources