SocialDataX TikTok MCP

tiktok_get_user_posts_by_profile_url

Read-only

根据 TikTok 用户主页链接获取作品列表，支持 page_token 翻页。

Input Schema

Name	Required	Description	Default
`page_token`	No	请求分页令牌是不透明令牌。请求的 page_token 为空字符串表示首页；继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。
`profile_url`	Yes	非空 TikTok 用户主页链接，例如 https://www.tiktok.com/@teamtrump

Output Schema

Name	Required	Description
`items`	Yes	当前页用户作品列表
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`next_page_token`	Yes	响应分页令牌是不透明令牌。响应的 next_page_token 为空字符串表示没有更多结果；非空时必须将完整令牌原样作为下一次请求的 page_token 传回；不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

addedOutput schema / properties / items / items / properties / is_pinned

Added value: +{
+  "default": false,
+  "description": "是否为主页置顶作品",
+  "type": "boolean"
+}

Changed5 schema fields changedOct 2, 2026

changedInput schema / properties / page_token / description

Previous value: -"分页令牌。首页传空字符串；next_page_token 为空字符串表示没有更多结果。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；它是不透明令牌，不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。"New value: +"请求分页令牌是不透明令牌。请求的 page_token 为空字符串表示首页；继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。"

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.*"
```

changedOutput schema / properties / next_page_token / description

Previous value: -"分页令牌。首页传空字符串；next_page_token 为空字符串表示没有更多结果。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；它是不透明令牌，不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。"New value: +"响应分页令牌是不透明令牌。响应的 next_page_token 为空字符串表示没有更多结果；非空时必须将完整令牌原样作为下一次请求的 page_token 传回；不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。"

First observedSep 1, 2026

TDQS

B3.4/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 profile is covered. The description adds one behavioral fact beyond that — pagination via page_token is supported — but says nothing about result volume, ordering, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the resource and the pagination capability front-loaded, and no filler. Nothing could be removed without losing information.

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?

With an output schema present and annotations covering safety, the return-value burden is lifted, and both parameters are fully documented in the schema. The remaining gap is routing guidance among the many sibling user/post retrieval tools.

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% and the page_token description in the schema is extremely detailed (opaque token, must be passed back verbatim, no cross-query reuse). The description merely restates that pagination exists, adding nothing beyond the schema, so the 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?

The description states a specific verb and resource ('获取作品列表' / fetch post list) scoped by input type ('根据 TikTok 用户主页链接'). This implicitly separates it from the sibling tiktok_get_user_posts_by_tiktok_id, but it never names the alternative explicitly, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no conditions or prerequisites, and no mention of when to pick this over tiktok_get_user_posts_by_tiktok_id or tiktok_search_posts. The only usable signal is the input type implied by the name and description.

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?