SiteCheck Shop & Social

Public TikTok profile from the profile page's embedded

social_tiktok_profile

Read-only

Public TikTok profile from the profile page's embedded data: user ID, secUid, nickname, bio, bio link, verified, private and organization flags, language, avatar, creation date, and exact counts of followers, following, likes, videos and friends. The page carries no video list for anonymous visitors, so videos are not included. Unknown usernames return 404. Related tools on this server, for a different need: social_tiktok_comments when you need Top-level comments of a public TikTok video from TikTok's; social_tiktok_hashtag_analytics when you need TikTok hashtag stats from TikTok's public hashtag detail. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description	Default
`username`	Yes	TikTok username (with or without @), or a tiktok.com/@user URL

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the anonymous-visitor limitation (no videos), the 404 failure mode, and the x402 payment mechanics including cost and no-charge-on-failure. These are exactly the operational facts an agent needs before spending money on a call.

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-loads the purpose and field list, then constraints, then alternatives and price — a sensible order. Slightly bloated by the long field enumeration and by the awkwardly truncated sibling clauses ('from TikTok's'), which read as generated filler.

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?

Covers what is returned at a field level, what is deliberately absent, error behavior, and cost. An output schema exists so return-value structure needn't be restated, and this is a single-parameter read tool, so nothing material is missing.

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 documents that the username may be given with or without '@' or as a tiktok.com URL. The description adds no further format or normalization detail, so the schema is doing all the work here.

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?

Names a specific verb and resource (public TikTok profile from the page's embedded data) and enumerates exactly which fields come back, so an agent knows the payload shape before calling. It also explicitly contrasts itself with social_tiktok_comments and social_tiktok_hashtag_analytics, which handle different resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the boundary conditions directly: no video list for anonymous visitors, 404 for unknown usernames, and names the two sibling tools to use for comments and hashtag stats instead. It also discloses the per-call price and that failures are not charged, giving the agent everything needed to decide whether to call.

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

All SiteCheck Shop & Social tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?