SocialDataX X / Twitter MCP

x_get_user_posts_by_user_id

Read-only

根据 X 用户 ID 获取公开用户帖子列表；已有完整 user_id 时直接使用，支持 page_token 翻页。

Input Schema

TableJSON Schema

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

Output Schema

TableJSON 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 / user_id / description

Previous value: -"X 用户稳定数字 ID；用户已提供时原样使用，否则可从搜索、详情、评论或评论回复结果的非空 author.user_id、用户帖子列表结果的非空 author.user_id，或用户信息结果的非空 user_id 原样复制；必须是数字字符串；不要传用户名、用户主页链接、帖子链接或分享文案。"New value: +"X 用户稳定数字 ID；用户已提供时原样使用；必须是数字字符串。可从用户搜索结果的非空 items[*].user_id、用户详情的非空 user_id，或帖子及评论结果的非空作者字段 author.user_id 原样复制；不要传用户名、用户主页链接、帖子链接或分享文案。"

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, so safety is covered. The description adds only that page_token pagination is supported, which is already fully spelled out in the schema; no extra context on rate limits, ordering, or result bounds is provided. A 3 fits given the lower bar set by annotations.

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 single compact sentence with the resource, the identifier precondition, and pagination front-loaded; nothing is padded. The trailing page_token clause is mildly redundant with the schema but cheap.

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?

An output schema exists so return values need not be described, and annotations cover the read-only/open-world profile. Purpose, required identifier, and pagination semantics are all present; the only gap is explicit routing to the username/profile_url siblings.

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%, and the two parameter descriptions are unusually thorough (exact-copy rules for user_id, opaque-token handling and reset-on-user-switch rules for page_token). The description adds nothing beyond the pagination mention, so the baseline 3 is 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+resource+scope: fetch a user's public post list by X user ID, with pagination support. The identifier form (user_id) implicitly separates it from the sibling *_by_username and *_by_profile_url variants, but the description never names those alternatives, so differentiation relies on the tool name.

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?

"已有完整 user_id 时直接使用" gives a usable trigger condition (you already have a complete numeric user_id). However, no explicit when-not or alternative routing is given, even though the sibling list contains three identically-purposed tools keyed by username and profile_url — the agent must infer the choice.

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?