Skip to main content
Glama

SocialDataX X / Twitter MCP

x_get_post_comments_by_post_id

Read-only

根据 X 帖子 ID 获取公开帖子的一级评论列表,不内嵌评论回复;已知 post_id 时优先使用,不要传帖子链接或评论 ID。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_idYesX 帖子 ID;用户已提供时原样使用,否则可从搜索结果、详情结果、quoted_post、reposted_post 或用户帖子列表结果复制 post_id;必须是数字字符串;不要传帖子链接、用户名、评论 ID 或分享文案。
page_tokenNoX 帖子评论列表分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一帖子评论列表;切换到其他帖子时请清空 page_token 后从第一页重新获取。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes当前页一级评论列表;当前页可能为空,是否可继续翻页以 next_page_token 是否为空为准。
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
post_urlYes所属帖子详情页链接;不是评论链接;不可用时为 null。
comment_countYes该帖子评论总数;不是当前页 items 数量;不可用时为 null。
next_page_tokenYes下一页不透明分页令牌;为空表示没有更多评论。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回;只用于当前帖子评论列表续页;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses that only top-level comments are returned and that the post must be public. It does not cover rate limits or auth, but the annotation burden is already partly satisfied.

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 front-loads the operation, scope, and key exclusions. Every clause earns its place with no redundant material.

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

Completeness5/5

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

With complete parameter documentation, an output schema, and safe-read annotations, the description covers what the tool does, when to use it, and its domain constraints. Pagination handling is already in the schema.

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 post_id and page_token are already thoroughly documented. The tool description adds minimal parameter semantics beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states a specific verb and resource: retrieving top-level comments for a public post by post ID, and explicitly notes replies are not embedded. This distinguishes it from siblings like x_get_post_comment_replies_by_comment_id and x_get_post_comments_by_post_url.

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

Usage Guidelines5/5

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

It says to prefer this tool when post_id is known and explicitly warns not to pass a post link or comment ID. This creates clear selection boundaries against the URL-based and reply-based sibling tools.

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