Skip to main content
Glama

SocialDataX X / Twitter MCP

by com.52choujiang
OverviewDiscussionsAdmin

x_get_user_posts_by_profile_url

Read-only

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

Input Schema

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

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / items / items / properties / is_pinned
      Added value: +{
+  "default": false,
+  "description": "是否为该用户主页中的置顶帖子。",
+  "type": "boolean"
+}
  2. Changed1 schema field 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 原样复制；不要传帖子链接、评论链接、帖子正文里的链接、搜索关键词或接口地址。"
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral context: pagination via page_token, first-page/onward semantics, and the requirement to pin the token to a single user. It does not describe volume or rate limits, but for a read-only list tool this is adequate.

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?

Front-loaded with the purpose, then the sourcing constraint, then pagination support. Dense but every clause carries information; minor redundancy with the schema's profile_url 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?

An output schema exists, so return shape need not be explained. With annotations covering the safety profile and 100% schema coverage, the description supplies the remaining context an agent needs to select and call this correctly.

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 page_token and profile_url are already fully documented in the schema, including the opaque-token rules. The description restates the accepted source fields for profile_url and the post-link exclusion, which reinforces but does not exceed 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?

Names a specific verb and resource (obtain public user post list by profile URL) and implicitly distinguishes it from the user_id/username siblings that fetch the same resource. An agent can tell what it retrieves without opening the schema.

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?

Explicitly tells the agent where to source profile_url (user search items[*].profile_url, user detail profile_url, or author.profile_url) and warns against passing post links. It does not, however, state when to prefer this over x_get_user_posts_by_user_id or _by_username, which are the more likely point of confusion.

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 toolsInspect
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