Skip to main content
Glama

Estimate TikTok earnings

estimate_tiktok_earnings
Read-onlyIdempotent

Estimate a TikTok creator's monthly income from Creator Rewards views, LIVE gifts (diamonds) and brand deals. TikTok publishes none of these rates, so every rate is an editable assumption: $0.50 per 1,000 qualified views, $0.005 per diamond and $10 per 1,000 followers per sponsored post by default.

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_tiktok_earnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpmNoUSD per 1,000 qualified views (assumption).
diamondsNoLIVE gift diamonds per month.
followersNo
diamond_valueNoUSD per diamond (assumption).
qualified_viewsNoQualified Creator Rewards views per month.
sponsored_postsNoSponsored posts per month.
usd_per_1000_followersNoBrand deal rate per sponsored post (assumption).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them: the rates are not published by TikTok, they are assumptions the caller controls, which prevents an agent from treating the output as authoritative. It stops short of saying what the result contains (total only or per-stream breakdown).

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 what is estimated and followed by the assumption framing. The second sentence repeats default values that the schema already carries, which is mildly redundant but earns its place by making overrideability obvious at a glance.

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?

A seven-parameter calculator with no output schema needs the description to say what comes back; it only implies a single monthly income figure and never states currency, whether a per-stream breakdown is returned, or that the result is gross and excludes fees/taxes. The assumption framing partly compensates, but the return-shape gap remains.

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 86%, so the schema already documents nearly every parameter including the '(assumption)' tags. The description restates three defaults (rpm, diamond_value, usd_per_1000_followers) inline, which is a fast skim but adds little meaning beyond the schema, and it says nothing about followers, diamonds, qualified_views or sponsored_posts.

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 TikTok creator's monthly income', and enumerates the three revenue streams it models (Creator Rewards views, LIVE gifts, brand deals). The explicit platform naming separates it cleanly from the sibling estimators estimate_kick_earnings and estimate_twitch_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?

Usage is implied rather than stated: the framing that TikTok publishes no rates and all rates are editable assumptions signals this is a hypothetical what-if calculator, not a lookup. There is no explicit when-to-use, when-not-to-use, or pointer to convert_tiktok_coins for the coin/diamond conversion step.

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