SiteCheck Shop & Social

Public X profiles for up to 10 usernames via the free

social_x_com_profiles

Read-only

Public X (Twitter) profiles for up to 10 usernames via the free FxTwitter API (open-source relay of X's public profile data; X's own API is paid): user ID, name, bio with expanded links, location, website, join date, protected flag, verification (verified + type: individual, business, government), followers, following, posts, likes, media count, avatar and banner. Unknown or suspended usernames go to notFound. Usually answers in a few seconds, up to 26 s on slower calls; allow a 45 s timeout. Related tools on this server, for a different need: social_x_com when you need one public X post by URL or ID from the JSON behind X's; social_instagram_related_profiles when you need Accounts Instagram suggests as related to a public profile. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "usernames": "<usernames>"
    },
    "name": "social_x_com_profiles"
  }
}

Input Schema

Name	Required	Description	Default
`usernames`	Yes	1 to 10 X usernames, comma separated, with or without @ (x.com/<user> URLs accepted)

Output Schema

Name	Required	Description	Default
`count`	No
`source`	No
`notFound`	No
`profiles`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Well beyond the readOnlyHint/openWorldHint annotations, it discloses the pricing model ($0.002 USDC per successful call, failures uncharged), the payment rails, the expected latency with a 45 s timeout recommendation, and the notFound behavior for unknown or suspended usernames. It also names the upstream source, so the agent knows the data is a third-party relay rather than X's paid API.

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?

Dense but front-loaded: scope first, then returned fields, edge cases, latency, alternatives, and pricing. It is one long run-on passage with some parenthetical clutter (API explanation, payment rails), but essentially every sentence carries actionable information.

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?

An output schema already covers return values, yet the description still summarizes the field set and, more importantly, covers cost, latency, timeout, and the notFound path an agent must handle. For a single-parameter paid lookup tool, nothing needed to invoke it correctly is missing.

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 coverage is 100% and the single parameter already documents the comma-separated 1–10 username format with optional @ and URL acceptance. The description restates the 'up to 10 usernames' limit but adds no format detail beyond the schema, so the baseline 3 applies.

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?

States a specific resource (public X/Twitter profiles), a precise scope (up to 10 usernames, public data only), and names the data source (FxTwitter relay). It is clearly distinguishable from the sibling social_x_com, which handles single posts by URL/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?

It explicitly routes two adjacent needs elsewhere (social_x_com for one post by URL/ID, social_instagram_related_profiles for Instagram suggestions) and gives a latency/timeout expectation. It stops short of stating exclusions inside its own domain, e.g. whether to prefer this over social_x_com for lookups by numeric user ID only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SiteCheck Shop & Social 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?