SocialDataX X / Twitter MCP

x_get_user_info_by_username

Read-only

根据 X 用户名获取公开用户信息；可使用用户搜索结果的非空 items[*].username，或帖子及评论结果的非空 author.username。

Input Schema

Name	Required	Description	Default
`username`	Yes	X 用户名，不带 @；也接受用户提供的 @username。可从用户搜索结果的非空 items[*].username、用户详情的非空 username，或帖子及评论结果的非空作者字段 author.username 原样复制；不要传用户主页链接、帖子链接或分享文案。

Output Schema

Name	Required	Description
`bio`	Yes	用户个人简介；没有或不可用时为空字符串。
`name`	Yes	用户展示名；不是 username；不可用时为空字符串。
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`user_id`	Yes	X 用户稳定数字 ID；不可用时为空字符串。
`location`	Yes	用户主页资料里填写的所在地；不是 IP 属地；不可用时为空字符串。
`username`	Yes	X 用户名，不带 @；不可用时为空字符串。
`avatar_url`	Yes	头像链接；不可用时为 null。
`is_private`	Yes	是否私密/受保护账号；不可用时为 null。
`post_count`	Yes	累计发帖数；不可用时为 null。
`is_verified`	Yes	是否显示 X 认证标识；不可用时为 null。
`profile_url`	Yes	用户主页链接；不可用时为 null。
`external_url`	Yes	用户主页填写的网站或外部链接；不是用户主页链接；标准用户主页请使用 profile_url；不可用时为 null。
`verified_type`	Yes	认证类型补充文本；不用于判断是否认证，应以 is_verified 为准；没有或不可用时为 null。
`follower_count`	Yes	粉丝数；不可用时为 null。
`following_count`	Yes	关注数；不可用时为 null。
`pinned_post_ids`	Yes	置顶帖子 ID 列表；可用于 x_get_post_detail_by_post_id；没有或不可用时为空数组。
`header_image_url`	Yes	用户主页头图链接；不可用时为 null。
`media_post_count`	Yes	累计媒体帖数；不可用时为 null。
`account_created_time`	Yes	账号创建时间，秒级 Unix 时间戳；不可用时为 null。
`affiliated_account_count`	Yes	该账号关联的账号数量；不可用时为 null。

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields 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 原样复制；不要传用户主页链接、帖子链接或分享文案。"

changedOutput schema / required

Previous value: -[
-  "user_id",
-  "username",
-  "name",
-  "avatar_url",
-  "profile_url",
-  "bio",
-  "external_url",
-  "is_verified",
-  "verified_type",
-  "is_private",
-  "affiliated_account_count",
-  "follower_count",
-  "following_count",
-  "post_count",
-  "media_post_count",
-  "location",
-  "header_image_url",
-  "pinned_post_ids",
-  "account_created_time",
-  "points"
-]New value: +[
+  "user_id",
+  "username",
+  "name",
+  "avatar_url",
+  "profile_url",
+  "bio",
+  "external_url",
+  "is_verified",
+  "verified_type",
+  "is_private",
+  "follower_count",
+  "following_count",
+  "post_count",
+  "media_post_count",
+  "location",
+  "header_image_url",
+  "pinned_post_ids",
+  "account_created_time",
+  "affiliated_account_count",
+  "points"
+]

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 the safety profile is covered. The description adds only that the data is '公开' (public), which is mild scope context, and says nothing about permissions, rate limits, or lookup failure behavior; with annotations present, this is adequate but not rich.

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 front-loaded sentence that leads with the verb and resource, then appends the sourcing hint. It is tight with no obvious filler, though the sourcing detail partially duplicates the schema.

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 single-parameter lookup tool with an output schema and full annotation coverage, the description supplies the essential purpose and input sourcing guidance. The only missing piece is explicit routing among the many sibling lookup-by-X tools.

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 the schema already documents format ('不带 @', accepts '@username'), sourcing, and negative cases (no links or share text). The description largely restates the same sourcing paths, adding little beyond the schema; 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 and resource ('根据 X 用户名获取公开用户信息' – get public user info by X username), which is unambiguous about what the tool returns. It does not, however, explicitly contrast itself with the sibling lookup modes (by_profile_url, by_user_id), leaving the agent to infer the routing from the name alone.

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 a valid username can be sourced from (search result items[*].username, or author.username from posts/comments), which is implied usage guidance. It never states when to prefer this lookup over x_get_user_info_by_user_id or x_get_user_info_by_profile_url, so the alternative-selection guidance is absent.

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?