Skip to main content
Glama

SocialDataX X / Twitter MCP

x_get_user_info_by_profile_url

Read-only

根据 X 用户主页链接获取公开用户信息;可使用用户搜索结果的非空 items[*].profile_url,或帖子及评论结果的非空 author.profile_url。不要传帖子链接。

Input Schema

NameRequiredDescriptionDefault
profile_urlYesX 用户主页链接;也接受用户提供的 x.com 或 twitter.com 用户主页链接。可从用户搜索结果的非空 items[*].profile_url、用户详情的非空 profile_url,或帖子及评论结果的非空作者字段 author.profile_url 原样复制;不要传帖子链接、评论链接、帖子正文里的链接、搜索关键词或接口地址。

Output 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. Changed2 schema fields changed
    • changedInput schema / properties / profile_url / description
      Previous value: -"X 用户主页链接;从搜索、详情、评论或评论回复结果的非空 author.profile_url,或用户帖子列表结果的非空 author.profile_url,或用户信息结果的非空 profile_url 原样复制;也可传用户提供的 x.com 或 twitter.com 用户主页链接;不要传帖子链接、评论链接、帖子正文里的链接、搜索关键词或接口地址。"New value: +"X 用户主页链接;也接受用户提供的 x.com 或 twitter.com 用户主页链接。可从用户搜索结果的非空 items[*].profile_url、用户详情的非空 profile_url,或帖子及评论结果的非空作者字段 author.profile_url 原样复制;不要传帖子链接、评论链接、帖子正文里的链接、搜索关键词或接口地址。"
    • 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"
      +]
  2. First observed

TDQS

A3.6/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 that the returned data is "公开" (public) info, which is mildly useful, but nothing about rate limits, auth, or response shape. With annotations carrying the behavioral load, a 3 is appropriate.

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 states purpose first, then input sources, then the exclusion. Efficient, though it overlaps noticeably with the parameter's own schema description.

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 and annotations covering safety, the description need not explain return values. It adequately covers the one input's provenance and a key misuse case, leaving only sibling routing unspecified.

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 single parameter's schema text already documents accepted URL forms and the exclusion list. The description largely restates that same guidance, so it adds no meaning beyond the schema – baseline 3.

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 用户主页链接获取公开用户信息" – fetch public user info by profile URL), which naturally distinguishes it from the by_user_id and by_username siblings. It does not explicitly call out those alternatives, so differentiation is implicit via the input type rather than stated.

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?

Gives concrete guidance on where to source the input (non-empty items[*].profile_url from user search, or author.profile_url from posts/comments) and an explicit exclusion ("不要传帖子链接"). Clear context for use, though it never names the by_user_id/by_username alternatives that would be the fallback when a URL is unavailable.

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