Skip to main content
Glama

SocialDataX X / Twitter MCP

x_get_post_detail_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 帖子页面链接;不要传用户主页链接、帖子正文里的链接、搜索关键词或接口地址。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
langYes帖子语言代码;不可用时为空字符串。
textYes帖子正文文本;不可用时为空字符串。
authorYes帖子作者信息;不可用时为 null。
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
post_idYesX 帖子数字 ID;帖子详情或评论列表查询优先使用该字段;请按字符串原样保留。
post_urlYesX 帖子详情页链接;主要用于展示;详情或评论列表查询优先使用 post_id,只有没有 post_id 时再作为 URL 入口;不是帖子正文里的链接;不可用时为 null。
post_typeYes帖子类型;text=未返回图片/视频媒体的文字帖,photo=图片帖,video=包含视频的帖子。
like_countYes该帖累计点赞数;不可用时为 null。
topic_tagsYes帖子中的话题标签;无话题标签或不可用时为空数组;每项只返回 name,不带 #。
view_countYes该帖累计浏览/观看数;不可用时为 null。
media_countYes帖子包含的媒体数量;等于返回的 media_items 数量。
media_itemsYes帖子包含的图片/视频媒体列表;无媒体或不可用时为空数组。
quote_countYes该帖被引用次数;不是 quoted_post 对象数量;不可用时为 null。
quoted_postYes被引用的帖子摘要;不是完整帖子详情结构;没有引用帖或不可用时为 null。
reply_countYes该帖累计回复/评论统计;不是评论列表当前页 items 数量;不可用时为 null。
is_sensitiveYes是否带有平台敏感内容标记;不可用时为 null。
publish_timeYes发布时间,秒级 Unix 时间戳;不可用时为 null。
repost_countYes该帖累计转帖数;不可用时为 null。
reposted_postYes被转帖的原帖摘要;不是引用帖,也不是完整帖子详情结构;没有转帖原帖或不可用时为 null。
bookmark_countYes该帖累计书签数;不可用时为 null。
external_linksYes帖子正文中的链接列表;可能包含外部网站或 X 内部链接;无链接或不可用时为空数组。
conversation_idYes会话/讨论串归组 ID;不是评论 ID;不可用时为空字符串。
cover_image_urlYes帖子首个可用媒体封面图链接;无媒体或不可用时为 null。
mentioned_usersYes帖子中 @ 到的用户;无 @ 或不可用时为空数组。
reply_to_post_idYes该帖回复的上级帖子 ID;不是评论 ID;没有或不可用时为空字符串。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/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. The description adds the 'public post' qualifier, which is useful context. It does not contradict annotations and doesn't need to repeat read-only nature. Minor missing disclosure about rate limits or authentication is acceptable given annotations cover safety.

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 main description is a single, dense sentence that conveys purpose and usage condition in parallel. The parameter description is verbose but necessary for correctness. Nothing superfluous.

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 one parameter, an output schema present, and annotations covering read-only behavior, the description covers purpose, usage conditions, and parameter semantics completely. Nothing an agent needs to invoke correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The parameter description is exceptionally thorough, detailing what constitutes a valid post_url and explicitly listing what not to pass (user profile links, links in post body, keywords, API endpoints). This far exceeds the basic schema description and fully compensates for any ambiguity.

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?

The description clearly states the tool fetches public post details from a post link, with the specific condition that it is only used when no post_id is available. It distinguishes from the sibling x_get_post_detail_by_post_id by making the post_id condition explicit.

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?

Explicitly states when to use: only when there is no post_id, only a post_link, or when using a non-empty post_url from results. This routes the agent clearly away from the by_post_id sibling and toward using URL-based data.

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