Skip to main content
Glama

SocialCaptain Creator Tools

TikTok earnings estimate

tiktok_earnings_estimate
Read-onlyIdempotent

Estimate a month of TikTok income in US dollars from Creator Rewards (needs 10,000 followers and 100,000 views in 30 days), sponsored videos (by follower tier) and LIVE gifts. Returns low and high figures and says which Creator Rewards minimums are missing. Rates are public estimates, not guarantees.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "followers": "<followers>",
      "average_views": "<average_views>",
      "videos_per_month": "<videos_per_month>"
    },
    "name": "tiktok_earnings_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
followersYesFollower count.
average_viewsYesAverage views per video of one minute or longer.
videos_per_monthYesVideos of one minute or longer posted a month.
live_diamonds_per_monthNoDiamonds received from LIVE gifts a month. Default 0.
sponsored_videos_per_monthNoSponsored videos a month. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive traits, so the bar is lower; the description nonetheless adds real context by stating that both low and high figures are returned, that missing Creator Rewards minimums are reported, and that all rates are public estimates rather than guarantees.

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 dense sentences, front-loaded with the core action, then prerequisites, then the return shape and disclaimer; nothing is repeated from the schema or wasted.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so (low/high figures, missing minimums), and it covers required eligibility thresholds plus the estimate caveat, which is everything needed to call a 5-parameter calculation tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by tying inputs to outputs: followers gate Creator Rewards eligibility, sponsored video rates vary by follower tier, and live_diamonds_per_month feeds LIVE gifts, which explains why the optional parameters matter.

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 month of TikTok income in US dollars") and enumerates the three revenue streams it models, which cleanly separates it from instagram_earnings_estimate and the tiktok_statistics siblings.

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?

It gives the eligibility conditions for Creator Rewards (10,000 followers, 100,000 views in 30 days), which implicitly tells the agent when the estimate will flag missing minimums, but it never names an alternative tool or says when to prefer a different estimator.

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