Skip to main content
Glama

SocialDataX TikTok MCP

tiktok_get_post_comments_by_post_id

Read-only

根据 TikTok 作品 post_id 获取一级评论,支持 page_token 翻页。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYesTikTok 作品 post_id;用户已提供时直接使用,否则可使用 tiktok_search_posts 返回的 content_type=video 或 image 的 post_id;读取评论回复时也可使用评论列表 items[*].post_id;长数字字符串,原样传入,不要转为数字
page_tokenNo请求分页令牌是不透明令牌。请求的 page_token 为空字符串表示首页;继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;不能修改、截断、脱敏、格式化、重组,也不能跨关键词、筛选条件或不同请求链路复用。

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 传回;不能修改、截断、脱敏、格式化、重组,也不能跨关键词、筛选条件或不同请求链路复用。"
    • 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

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, covering the safety profile. The description adds that it retrieves top-level comments and supports page_token pagination, which is useful but limited; it does not disclose rate limits, auth needs, or failure 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 zero waste. It states the action, input, and a key pagination feature concisely.

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?

Given the simple read operation, full schema coverage, annotations, and an output schema, the description is almost complete. It clearly states what is returned (top-level comments) and how to page, though it could briefly mention that replies are handled by a separate tool.

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%, so the schema fully documents both parameters. The description only mentions post_id and page_token pagination, adding no meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 (一级评论) scoped to TikTok post_id, implicitly distinguishing from siblings that fetch by URL or fetch replies. However, it does not explicitly name or contrast with those alternative tools, so it falls short of full 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 Guidelines2/5

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

The description implies the tool is used when you have a post_id, but provides no guidance on when to prefer it over tiktok_get_post_comments_by_url or tiktok_get_post_comment_replies. No prerequisites or exclusions are mentioned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources