ScrapingDog-MCP

tiktok_profile

Fetch TikTok user profile data including followers, engagement metrics, bio, and account metadata by providing a username.

Instructions

Scrapes comprehensive profile data for any TikTok user including follower counts, engagement metrics, bio, avatar URLs, and account metadata. [Credits: 5 API credits per successful request] Notes: username is the TikTok handle without the @ symbol. Returns: { id, username, nickname, sec_uid, bio, profile_url, verified, private_account, followers, following, likes, video_count, region, language, avatar, avatar_medium, avatar_large, created_at, is_commerce_account, commerce_category, is_organization, duet_setting, stitch_setting, comment_setting, download_setting }

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": {
      "username": "<username>"
    },
    "name": "tiktok_profile"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes	The username of the TikTok profile to scrape (e.g., `nike`, `mrbeast`).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations exist, so description carries full weight. Mentions credit cost (5 per request) and lists all return fields comprehensively. No hidden behaviors like auth requirements or rate limits are disclosed.

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?

Description is 4 sentences with clear structure: purpose, credit note, formatting note, return data. Could be slightly trimmed, but every sentence adds value.

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?

No output schema exists, so the detailed list of return fields is essential and provided. Lacks error handling or additional limitations, but given the tool's simplicity (single parameter, no pagination), it is sufficiently complete.

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% with one parameter already described well. Description adds value by clarifying 'username is the TikTok handle without the @ symbol', which is a helpful nuance beyond the schema's examples.

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?

Clear verb 'scrapes' with specific resource 'profile data for any TikTok user' and lists key data types (follower counts, engagement metrics, etc.). Distinguishes from siblings like tiktok_post and tiktok_ads by focusing on profile-level data.

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?

States the tool is for 'any TikTok user' and notes credit cost and username format, but does not explicitly contrast with alternatives or provide when-not-to-use guidance. Siblings include other TikTok tools, but no direct comparison.

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

Deploy Server