ScrapeCreators MCP Server

User's Audience Demographics

tiktok_audience_demographics

Fetch TikTok follower locations by country to analyze audience geography; returns counts and percentages per country for a given handle.

Instructions

Retrieves audience demographic data for a TikTok user, showing where their followers are located by country. Returns audienceLocations, an array of objects each containing country, countryCode, count, and percentage. Costs 26 credits per request. Potentially consumes paid API credits; requires confirm=true. Read-like POST requests do not publish to social platforms.

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": {
      "handle": "<handle>"
    },
    "name": "tiktok_audience_demographics"
  }
}

Input Schema

Name	Required	Description
`handle`	Yes	TikTok handle
`account`	No	Named private ScrapeCreators account; selects credentials, not a remote account ID.
`confirm`	No	Must be true for the specific approved credit-consuming research call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds real value beyond that: a per-request credit cost, the mandatory confirm=true gate, and an explicit clarification that these read-like POSTs do not publish to social platforms, which resolves the tension with readOnlyHint=false.

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?

Front-loaded with purpose, then return shape, then cost/consent caveat — a logical order with little waste. The final sentence about read-like POST requests is slightly tangential but earns its place by reconciling with readOnlyHint=false.

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 compensates by naming the returned audienceLocations array and its fields (country, countryCode, count, percentage), and it covers the cost and consent constraints. An agent has everything needed to invoke 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?

Schema description coverage is 100%, so handle, account, and confirm are already documented in the schema; baseline is 3. The description reinforces the confirm requirement and the credit cost but adds no syntax or format detail beyond the structured fields.

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 (retrieves) and resource (audience demographic data / follower locations by country) for a TikTok user, and names the exact fields returned. This clearly separates it from siblings like tiktok_followers or tiktok_profile_region, which return different data shapes.

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 description implies usage (fetch follower location breakdown for a given handle) and adds a strong pre-condition (confirm=true, 26 credits per request), but never states when to prefer this over alternatives such as tiktok_profile_region or tiktok_followers. No exclusions or routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server