Skip to main content
Glama

SocialCaptain Creator Tools

TikTok statistics

tiktok_statistics
Read-onlyIdempotent

Current TikTok statistics, each as a quotable sentence with its value, year, scope and primary source (publisher, title, URL, date we checked it). Users, demographics, time spent, news use, engagement rates, formats, creator earnings and advertising. Pass a topic to narrow it down. Figures are re-checked regularly and come from platforms, public bodies and research institutes. Free to cite with a link to the page.

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

Input Schema

NameRequiredDescriptionDefault
topicNoOptional topic or question, for example 'engagement rate', 'teens' or 'creators earn'. Omit for the key statistics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, all consistent with a curated reference dataset. The description adds genuine context beyond them: figures are re-checked regularly, sources are platforms/public bodies/research institutes, and results are citation-ready with a link. It does not say what happens when a topic matches nothing or how many sentences come back.

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 opening sentence front-loads what the tool returns and in what form; the topic hint follows. The domain list is dense but scannable, and the licensing sentence is short and purposeful. Minor redundancy between 'Pass a topic to narrow it down' and the schema's own note.

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 one-optional-parameter read tool with no output schema and strong annotations, the description covers output format, provenance, freshness and licensing — everything an agent needs to use the results. The only real gap is unspecified behavior for unmatched or overly narrow topics.

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 coverage is 100%, and the schema already supplies the topic examples ('engagement rate', 'teens', 'creators earn') and the omit-for-defaults rule. The description's topic list echoes the schema rather than extending it with matching behavior or fallback semantics, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (TikTok statistics) and enumerates the covered domains: users, demographics, time spent, news use, engagement rates, formats, creator earnings and advertising. It also states the output shape (quotable sentence with value, year, scope and source). It does not differentiate itself from siblings like tiktok_earnings_estimate or best_time_to_post, which overlap in subject matter.

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?

'Pass a topic to narrow it down' plus the schema note 'Omit for the key statistics' gives basic usage of the single parameter. There is no guidance on when to prefer this over tiktok_earnings_estimate for creator-pay questions, or over engagement-rate-style siblings, so the agent must infer boundaries.

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