Skip to main content
Glama

SocialDataX X / Twitter MCP

x_get_user_info_by_username

Read-only

根据 X 用户名获取公开用户信息;可直接使用搜索、详情、评论或评论回复结果里的非空 author.username。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesX 用户名;推荐从搜索、详情、评论或评论回复结果的非空 author.username,或用户帖子列表结果的非空 author.username,或用户信息结果的非空 username 原样复制,该值不带 @;如果用户给的是 @username 也可以传;不要传用户主页链接、帖子链接或分享文案。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioYes用户个人简介;没有或不可用时为空字符串。
nameYes用户展示名;不是 username;不可用时为空字符串。
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
user_idYesX 用户稳定数字 ID;不可用时为空字符串。
locationYes用户主页资料里填写的所在地;不是 IP 属地;不可用时为空字符串。
usernameYesX 用户名,不带 @;不可用时为空字符串。
avatar_urlYes头像链接;不可用时为 null。
is_privateYes是否私密/受保护账号;不可用时为 null。
post_countYes累计发帖数;不可用时为 null。
is_verifiedYes是否显示 X 认证标识;不可用时为 null。
profile_urlYes用户主页链接;不可用时为 null。
external_urlYes用户主页填写的网站或外部链接;不是用户主页链接;标准用户主页请使用 profile_url;不可用时为 null。
verified_typeYes认证类型补充文本;不用于判断是否认证,应以 is_verified 为准;没有或不可用时为 null。
follower_countYes粉丝数;不可用时为 null。
following_countYes关注数;不可用时为 null。
pinned_post_idsYes置顶帖子 ID 列表;可用于 x_get_post_detail_by_post_id;没有或不可用时为空数组。
header_image_urlYes用户主页头图链接;不可用时为 null。
media_post_countYes累计媒体帖数;不可用时为 null。
account_created_timeYes账号创建时间,秒级 Unix 时间戳;不可用时为 null。
affiliated_account_countYes该账号关联的账号数量;不可用时为 null。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true, so this is known to be a non-destructive lookup. The description adds that the data is public, but does not disclose additional behavioral details such as rate limits or error behavior. It does not contradict 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 a single compact sentence with the verb and resource front-loaded. It communicates the core purpose and a practical usage hint without any extraneous content.

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?

This is a simple single-parameter read-only lookup with an output schema. The description, combined with the detailed parameter schema and annotations, provides enough information for an agent to call it correctly. No material gaps remain.

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 schema already explains valid username formats, the '@' handling, and what not to pass. The description merely echoes a subset of that guidance, so it does not add meaningful semantic value beyond the schema.

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 action and resource: getting public user information by X username. It also indicates the source of valid usernames, and the 'by_username' scoping distinguishes it from sibling tools that take a profile URL or user ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use the tool: when you have a non-empty author.username from search, detail, comment, or reply results. It does not explicitly say to use the profile_url or user_id siblings when those identifiers are available, but the intended input source is clear.

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