SocialDataX X / Twitter MCP

x_get_user_posts_by_username

Read-only

根据 X 用户名获取公开用户帖子列表；可使用用户搜索结果的非空 items[*].username，或帖子及评论结果的非空 author.username。支持 page_token 翻页。

Input Schema

Name	Required	Description	Default
`username`	Yes	X 用户名，不带 @；也接受用户提供的 @username。可从用户搜索结果的非空 items[*].username、用户详情的非空 username，或帖子及评论结果的非空作者字段 author.username 原样复制；不要传用户主页链接、帖子链接或分享文案。
`page_token`	No	X 用户帖子列表分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一用户帖子列表；切换 user_id、username 或 profile_url 时请清空 page_token 后从第一页重新获取。

Output Schema

Name	Required	Description
`items`	Yes	当前页 X 用户帖子列表；当前页可能为空，是否可继续翻页以 next_page_token 是否为空为准。
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`next_page_token`	Yes	下一页不透明分页令牌；为空表示没有更多用户帖子。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回；只用于当前用户帖子列表续页；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

addedOutput schema / properties / items / items / properties / is_pinned

Added value: +{
+  "default": false,
+  "description": "是否为该用户主页中的置顶帖子。",
+  "type": "boolean"
+}

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / username / description

Previous value: -"X 用户名；推荐从搜索、详情、评论或评论回复结果的非空 author.username，或用户帖子列表结果的非空 author.username，或用户信息结果的非空 username 原样复制，该值不带 @；如果用户给的是 @username 也可以传；不要传用户主页链接、帖子链接或分享文案。"New value: +"X 用户名，不带 @；也接受用户提供的 @username。可从用户搜索结果的非空 items[*].username、用户详情的非空 username，或帖子及评论结果的非空作者字段 author.username 原样复制；不要传用户主页链接、帖子链接或分享文案。"

First observedSep 1, 2026

TDQS

A3.5/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 only public posts are returned and that pagination is supported via page_token, which is modest additional context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A compact two-clause sentence that front-loads the core purpose before the parameter-sourcing detail. No wasted wording, though it is terse.

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?

With an output schema present, return values need not be explained, and the description covers username sourcing plus pagination adequately. It is complete enough for an agent to invoke correctly, missing only explicit sibling routing.

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 both username and page_token are already fully documented in the schema (including pagination-token handling rules). The description adds no meaning beyond what the schema provides, making the baseline 3 correct.

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 ('根据 X 用户名获取公开用户帖子列表'), making it clear this retrieves a user's posts by username. It does not, however, explicitly differentiate from siblings like x_get_user_posts_by_user_id or x_get_user_posts_by_profile_url, which the name alone must disambiguate.

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?

The description tells the agent where to source the username (user-search items[*].username or author.username from post/comment results), which is useful context. But it gives no guidance on when to prefer this tool over the by_user_id or by_profile_url variants, so selection among siblings is left to inference.

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

All SocialDataX X / Twitter MCP tools Inspect

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

Need Help?