Skip to main content
Glama

SocialDataX TikTok MCP

by com.52choujiang
OverviewDiscussionsAdmin

tiktok_get_user_posts_by_tiktok_id

Read-only

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tiktok_idYes非空 TikTok 号，即用户主页 @ 后的标识；可使用用户搜索结果中的 TikTok 号，也可使用其他搜索、详情、评论或评论回复结果中 author.tiktok_id 的值；不要带 @，不要传用户主页链接
page_tokenNo请求分页令牌是不透明令牌。请求的 page_token 为空字符串表示首页；继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。

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 / tiktok_id / description
      Previous value: -"TikTok 号，即用户主页 @ 后的标识；可直接使用搜索、详情、评论或评论回复结果中 author.tiktok_id 的值；不要带 @，不要传用户主页链接"New value: +"非空 TikTok 号，即用户主页 @ 后的标识；可使用用户搜索结果中的 TikTok 号，也可使用其他搜索、详情、评论或评论回复结果中 author.tiktok_id 的值；不要带 @，不要传用户主页链接"
    • addedInput schema / properties / tiktok_id / minLength
      Added value: +1
    • addedInput schema / properties / tiktok_id / 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.6/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 only that pagination via page_token is supported, which is already spelled out in the schema, and says nothing about result ordering, page size, or rate/credit behavior.

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 the resource first and the pagination capability second; every clause carries information and there is no filler.

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?

For a two-parameter read tool with a fully documented schema and an output schema covering return values, the description is sufficient to call it correctly. It would be stronger with a one-line note on the alternative by-profile-url tool or on how to detect the end of paging.

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 both parameters are documented in detail (format constraints for tiktok_id, opaque-token rules for page_token), so the baseline is 3. The description merely restates that page_token enables paging and adds no syntax 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 and resource (获取用户作品列表) plus the key it operates on (TikTok 号), so the agent knows exactly what it returns. It does not name the obvious sibling tiktok_get_user_posts_by_profile_url or explain how the two differ, so it falls short of the 5 tier.

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 key: the reader infers this is the right call when holding a tiktok_id rather than a profile URL. There is no explicit when-to-use / when-not-to-use statement and no reference to alternatives such as the profile_url variant.

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