SocialDataX X / Twitter MCP

x_search_users

Read-only

按关键词搜索 X / Twitter 用户，返回用户资料和分页令牌，支持 page_token 翻页。用于按名称发现账号；已知 user_id、username 或主页链接时，使用对应用户详情工具。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "x_search_users"
  }
}

Input Schema

Name	Required	Description	Default
`keyword`	Yes	用户搜索关键词或名称，例如 OpenAI；不要传用户 ID、主页链接或分页令牌。
`page_token`	No	首次请求留空；继续翻页时原样传入上次的 next_page_token，并保持 keyword 不变。

Output Schema

Name	Required	Description
`items`	Yes	匹配的用户列表；没有匹配时为空数组。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`next_page_token`	Yes	下一页令牌；为空字符串时停止翻页；继续查询时原样传入 page_token 并保持 keyword 不变。

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedOutput schema / properties / points / description

Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"

changedOutput schema / properties / points / properties / balance / description

Previous value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"

Changed2 schema fields changedNov 4, 2026
- changedOutput schema / properties / points / properties / balance / description
```
Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"
```
- removedOutput schema / properties / points / properties / balance / minimum
```
Removed value: -0
```
Changed22 schema fields changedNov 3, 2026
- addedOutput schema / properties / items / items / properties / account_created_time / title
```
Added value: +"Account Created Time"
```
- addedOutput schema / properties / items / items / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / items / items / properties / bio / title
```
Added value: +"Bio"
```
- addedOutput schema / properties / items / items / properties / external_url / title
```
Added value: +"External Url"
```
- addedOutput schema / properties / items / items / properties / follower_count / title
```
Added value: +"Follower Count"
```
- addedOutput schema / properties / items / items / properties / following_count / title
```
Added value: +"Following Count"
```
- addedOutput schema / properties / items / items / properties / header_image_url / title
```
Added value: +"Header Image Url"
```
- addedOutput schema / properties / items / items / properties / is_private / title
```
Added value: +"Is Private"
```
- addedOutput schema / properties / items / items / properties / is_verified / title
```
Added value: +"Is Verified"
```
- addedOutput schema / properties / items / items / properties / location / title
```
Added value: +"Location"
```
- addedOutput schema / properties / items / items / properties / media_post_count / title
```
Added value: +"Media Post Count"
```
- addedOutput schema / properties / items / items / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / items / items / properties / pinned_post_ids / title
```
Added value: +"Pinned Post Ids"
```
- addedOutput schema / properties / items / items / properties / post_count / title
```
Added value: +"Post Count"
```
- addedOutput schema / properties / items / items / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / items / items / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / items / items / properties / username / title
```
Added value: +"Username"
```
- addedOutput schema / properties / items / items / properties / verified_type / title
```
Added value: +"Verified Type"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"XUserSearchItemData"
```
- addedOutput schema / properties / items / title
```
Added value: +"Items"
```
- addedOutput schema / properties / next_page_token / title
```
Added value: +"Next Page Token"
```
- addedOutput schema / title
```
Added value: +"XUserSearchResult"
```
AddedOct 8, 2026

TDQS

A4.5/5.0

Behavior4/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 useful behavior beyond that — that results include user profiles plus a pagination token — and explains the paging contract. It stops short of noting result caps, rate limits, or matching semantics (exact vs fuzzy name match), which would be valuable for an open-world search.

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?

Two compact sentences: the capability and return shape come first, the routing rule second. Every clause carries information and nothing is repeated.

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?

For a two-parameter read-only search with a full output schema and 100% schema coverage, the description supplies everything an agent needs: the query form, the paging loop, and the disambiguation rule against detail 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%: the keyword property already says not to pass user IDs, profile links, or page tokens, and page_token already says to echo next_page_token and keep keyword constant. The description only restates that paging is supported, adding 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource (按关键词搜索 X/Twitter 用户) plus what comes back (用户资料和分页令牌), and explicitly distinguishes this tool from the sibling x_get_user_info_by_* family. An agent can route to it without opening any schema.

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

Usage Guidelines5/5

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

It states both the positive case (按名称发现账号) and the negative case (已知 user_id、username 或主页链接时，使用对应用户详情工具), naming the alternative tool family. No inference required.

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?