SiteCheck Shop & Social

One public X post by URL or ID from the JSON behind X's

social_x_com

Read-only

One public X (Twitter) post by URL or ID from the JSON behind X's official embed widget: text, language, date, like and reply counts, edit status, reply-to, links, hashtags, mentions, photos and video (poster, duration, MP4 variants), quoted post, and the author (name, handle, blue check, label). Retweet, view and bookmark counts are not in this source. Timelines and search need X's paid API. Deleted or protected posts return 404. Related tools on this server, for a different need: social_x_com_profiles when you need public X profiles for up to 10 usernames via the free; social_labx_com when you need listings of one LabX seller from the seller's public. 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": {
      "post": "<post>"
    },
    "name": "social_x_com"
  }
}

Input Schema

Name	Required	Description	Default
`post`	Yes	Post URL (x.com or twitter.com /status/<id>) or numeric post ID

Output Schema

Name	Required	Description	Default
`id`	No
`url`	No
`lang`	No
`text`	No
`likes`	No
`links`	No
`video`	No
`author`	No
`edited`	No
`photos`	No
`quoted`	No
`source`	No
`replies`	No
`hashtags`	No
`mentions`	No
`checkedAt`	No
`createdAt`	No
`inReplyTo`	No
`possiblySensitive`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description names the data source (the JSON behind X's official embed widget), which explains why retweet, view, and bookmark counts are absent. It also discloses error behavior (deleted or protected posts return 404) and payment mechanics ($0.002 USDC via x402, failed calls not charged) – all behavior an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is well front-loaded and dense with useful scope, but the sibling-routing clauses are visibly truncated ("via the free", "from the seller's public") and read as broken, and the full field enumeration partly duplicates the existing output schema. Payment details are relevant but appended in a way that makes the block longer than needed.

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 one-parameter read tool with an output schema, the description covers everything an agent needs: what data is returned, what the source cannot supply, what happens on missing/protected posts, and what the call costs. There is no material gap left open.

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's description already covers "Post URL (x.com or twitter.com /status/<id>) or numeric post ID." The tool description only restates "by URL or ID" without adding format nuances such as whether mobile/query-string URLs are accepted, so it adds little 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?

"One public X (Twitter) post by URL or ID" gives a specific verb (retrieve one post), a precise scope (public, single, by URL/ID), and immediately enumerates the payload. It also rules out what it is not: timelines and search require the paid API, which separates it from sibling social_x_com_profiles and the other social_* tools.

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 explicit usage boundaries ("Timelines and search need X's paid API") and routes to alternatives with conditions: social_x_com_profiles "when you need public X profiles for up to 10 usernames" and social_labx_com "when you need listings of one LabX seller." Cost per call is also disclosed so the agent can weigh whether to invoke.

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?