SocialDataX TikTok MCP

tiktok_get_user_info_by_profile_url

Read-only

根据 TikTok 用户主页链接获取用户公开资料。

Input Schema

Name	Required	Description	Default
`profile_url`	Yes	非空 TikTok 用户主页链接，例如 https://www.tiktok.com/@teamtrump

Output Schema

Name	Required	Description
`bio`	Yes	用户简介；当前不可用时为空字符串
`name`	Yes	用户昵称；当前不可用时为空字符串
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`user_id`	Yes	TikTok 用户 ID；长数字字符串，原样保留，不要转为数字；当前不可用时为空字符串；不要用它代替 tiktok_id 或 profile_url
`verified`	No	用户是否为认证账号；未知时省略
`tiktok_id`	Yes	TikTok 号，即用户主页 @ 后的标识；当前不可用时为空字符串，为空时不要作为用户标识使用
`avatar_url`	Yes	用户头像链接；当前不可用时为 null
`profile_url`	Yes	用户主页链接；当前不可用时为 null
`follower_count`	No	粉丝数；未知时省略
`following_count`	No	关注数；未知时省略
`private_account`	No	用户账号是否为私密账号；未知时省略
`received_like_count`	No	用户作品累计获赞数；未知时省略
`posted_content_count`	No	用户已发布作品数；未知时省略

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedOutput schema / properties / points / description

Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"

changedOutput schema / properties / points / properties / balance / description

Previous value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"

Changed2 schema fields changedNov 4, 2026
- changedOutput schema / properties / points / properties / balance / description
```
Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"
```
- removedOutput schema / properties / points / properties / balance / minimum
```
Removed value: -0
```
Changed13 schema fields changedNov 3, 2026
- addedOutput schema / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / bio / title
```
Added value: +"Bio"
```
- addedOutput schema / properties / follower_count / title
```
Added value: +"Follower Count"
```
- addedOutput schema / properties / following_count / title
```
Added value: +"Following Count"
```
- addedOutput schema / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / posted_content_count / title
```
Added value: +"Posted Content Count"
```
- addedOutput schema / properties / private_account / title
```
Added value: +"Private Account"
```
- addedOutput schema / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / received_like_count / title
```
Added value: +"Received Like Count"
```
- addedOutput schema / properties / tiktok_id / title
```
Added value: +"Tiktok Id"
```
- addedOutput schema / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / verified / title
```
Added value: +"Verified"
```
- addedOutput schema / title
```
Added value: +"TikTokUserInfoData"
```

Changed17 schema fields changedOct 8, 2026

addedOutput schema / properties / follower_count / default
```
Added value: +null
```

changedOutput schema / properties / follower_count / description

Previous value: -"粉丝数；当前不可用时为 null"New value: +"粉丝数；未知时省略"

addedOutput schema / properties / following_count / default
```
Added value: +null
```

changedOutput schema / properties / following_count / description

Previous value: -"关注数；当前不可用时为 null"New value: +"关注数；未知时省略"

addedOutput schema / properties / posted_content_count / default
```
Added value: +null
```

changedOutput schema / properties / posted_content_count / description

Previous value: -"用户已发布作品数；当前不可用时为 null"New value: +"用户已发布作品数；未知时省略"

addedOutput schema / properties / private_account / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / private_account / default
```
Added value: +null
```

changedOutput schema / properties / private_account / description

Previous value: -"用户账号是否为私密账号"New value: +"用户账号是否为私密账号；未知时省略"

removedOutput schema / properties / private_account / type
```
Removed value: -"boolean"
```
addedOutput schema / properties / received_like_count / default
```
Added value: +null
```

changedOutput schema / properties / received_like_count / description

Previous value: -"用户作品累计获赞数；当前不可用时为 null"New value: +"用户作品累计获赞数；未知时省略"

addedOutput schema / properties / verified / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / verified / default
```
Added value: +null
```

changedOutput schema / properties / verified / description

Previous value: -"用户是否为认证账号"New value: +"用户是否为认证账号；未知时省略"

removedOutput schema / properties / verified / type
```
Removed value: -"boolean"
```

changedOutput schema / required

Previous value: -[
-  "user_id",
-  "tiktok_id",
-  "name",
-  "avatar_url",
-  "profile_url",
-  "bio",
-  "verified",
-  "private_account",
-  "follower_count",
-  "following_count",
-  "received_like_count",
-  "posted_content_count",
-  "points"
-]New value: +[
+  "user_id",
+  "tiktok_id",
+  "name",
+  "avatar_url",
+  "profile_url",
+  "bio",
+  "points"
+]

Changed3 schema fields changedOct 2, 2026

changedInput schema / properties / profile_url / description

Previous value: -"TikTok 用户主页链接，例如 https://www.tiktok.com/@teamtrump"New value: +"非空 TikTok 用户主页链接，例如 https://www.tiktok.com/@teamtrump"

addedInput schema / properties / profile_url / minLength
```
Added value: +1
```
addedInput schema / properties / profile_url / pattern
```
Added value: +".*\\S.*"
```

First observedSep 1, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile is covered. The description adds that only '公开资料' (public data) is returned, which is mildly useful context, but says nothing about behavior with private/deleted accounts, invalid URLs, or rate limits.

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?

A single short sentence with the resource and lookup key front-loaded and no filler. It is efficient, though almost too terse to route against siblings.

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?

Low complexity, one fully documented parameter, annotations present, and an output schema covering return values – so the description needn't explain results. The main omission is sibling differentiation against the TikTok-ID variant, which is a minor gap at this complexity level.

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?

With one parameter at 100% schema coverage and an inline example plus non-empty pattern, the schema carries the load. The description only restates that a profile link is the input, adding no format or edge-case meaning beyond the schema.

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+resource: fetch a user's public profile using a TikTok profile URL. The URL-based input distinguishes it implicitly from tiktok_get_user_info_by_tiktok_id, though the description never names that sibling.

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?

Usage is only implied by the phrase '根据...主页链接' – an agent can infer to use this when it has a profile URL. There is no explicit guidance on when to prefer tiktok_get_user_info_by_tiktok_id or tiktok_search_users instead, and no exclusions.

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

All SocialDataX TikTok MCP 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?