Skip to main content
Glama

SocialDataX X / Twitter MCP

x_get_post_comments_by_post_url

Read-only

根据 X 帖子链接获取公开帖子的一级评论列表,不内嵌评论回复;仅在没有 post_id、只有帖子链接或结果里的非空 post_url 时使用。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
post_urlYesX 帖子链接;仅在没有 post_id 时,请传搜索结果、详情结果、quoted_post 或 reposted_post 返回的非空 post_url,或用户帖子列表结果返回的非空 post_url,或形如 https://x.com/{username}/status/{post_id} 的 x.com 或 twitter.com 帖子页面链接;不要传用户主页链接、评论链接、帖子正文里的链接、搜索关键词或接口地址。
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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering safety. The description adds that it returns only top-level comments (not nested replies) and applies to public posts, which is valuable behavioral context beyond the annotations.

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?

The description is two concise sentences, front-loaded with the core purpose and usage condition. No redundant wording or filler; every phrase earns its place.

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 simple read-only tool with two well-documented parameters and an output schema, the description covers the primary usage condition, return scope, and the alternative tool. Minor gaps like error handling or rate limits are not critical given the schema and annotations are thorough.

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% with detailed explanations of post_url (including allowed sources and exclusions) and page_token (opaque pagination token with strict usage rules). The tool description itself does not add extra parameter semantics, so baseline 3 is appropriate.

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 clearly states the tool retrieves top-level comments for a public post given a post URL, explicitly excludes replies, and distinguishes from the post_id-based sibling. The verb '获取' and resource '一级评论列表' are specific and unambiguous.

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?

The description explicitly says to use this tool only when there is no post_id and only a post_url (or a non-empty post_url from results), effectively pointing to the sibling tool x_get_post_comments_by_post_id for the alternative case. This is clear, actionable usage guidance.

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