Skip to main content
Glama

SocialDataX TikTok MCP

by com.52choujiang
OverviewDiscussionsAdmin

tiktok_get_user_posts_by_profile_url

Read-only

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

Input Schema

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

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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 传回；不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。"
  2. First observed

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 external-network profile are known. The description adds only the pagination capability, which is a thin behavioral addition. No disclosure of rate limits, return shape, or ordering. With annotations covering the basics, a 3 is fair.

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, front-loaded sentence with zero waste. Everything stated is relevant and no padding is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with a full output schema and complete parameter schema coverage, the description is adequate but minimalist. It does not mention any constraints or differences from the near-identical sibling, leaving some ambiguity for selection.

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 schema description already thoroughly explains its opaque, unmodifiable, non-reusable nature. The description adds only the fact that page_token enables pagination, which is marginal value beyond the schema. 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 (作品列表) scoped by profile URL. However, it does not distinguish itself from the sibling tiktok_get_user_posts_by_tiktok_id, which likely retrieves the same resource by a different identifier. No explicit sibling differentiation.

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?

The mention of page_token pagination implies a usage context (fetching a paginated list), but there is no explicit guidance on when to use this tool versus the tiktok_id variant or other siblings. Usage is implied at best.

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 toolsInspect
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