ScrapeCreators MCP Server

Profile Region

tiktok_profile_region

Retrieve a public TikTok profile's region code (like US or MX) to determine its country; requires confirm=true because paid API credits may apply.

Instructions

Returns the TikTok region code for a public profile, like US for United States or MX for Mexico. 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_profile_region"
  }
}

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 disclose readOnlyHint=false, destructiveHint=false and openWorldHint=true; the description usefully explains that gap by noting these are 'read-like POST requests' that 'do not publish to social platforms,' plus the credit cost. It does not cover rate limits or error behavior, so it stops short of a 5.

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?

Two front-loaded sentences with zero filler: the first gives the purpose and sample output, the second the cost/confirmation constraint and the semantic reassurance about POST usage.

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 single-value lookup with a fully documented schema, the description covers purpose, prerequisites, and the behavioral oddity of a non-read-only POST. It lacks only error/failure behavior, which is a minor gap given no output schema exists.

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%, so handle, account, and confirm are fully documented in the schema. The description only echoes the confirm=true requirement, adding no syntax or format detail beyond the structured fields. 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?

States a specific verb and resource ('Returns the TikTok region code for a public profile') and even illustrates the output format with concrete examples (US, MX). It is clear what the tool does, though it does not name tiktok_profile or any sibling to differentiate itself explicitly.

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?

Gives a concrete prerequisite: 'Potentially consumes paid API credits; requires confirm=true.' That tells the agent when this call is appropriate and what gate it must clear, but it offers no alternatives or when-not-to-use guidance relative to the many sibling profile tools.

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

Deploy Server