SiteCheck Shop & Social

Truth Social account and its latest posts: profile and up

social_truthsocial

Read-only

Truth Social account and its latest posts: profile (name, followers, following, post count, verified, website, joined) and up to 20 newest posts with text, time, replies, reposts, likes, media URLs, link card and repost/quote flags. From truthsocial.com's public Mastodon-style API through a residential proxy. Usually answers in about 9 s, up to 16 s on slower calls; allow a 30 s timeout. Related tools on this server, for a different need: social_pinterest when you need latest pins of a public Pinterest profile from Pinterest's; social_instagram when you need engagement snapshot of a public Instagram account. Price: $0.003 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": {
      "handle": "<handle>"
    },
    "name": "social_truthsocial"
  }
}

Input Schema

Name	Required	Description
`limit`	No	How many posts, 0 to 20 (default 10; 0 = profile only)
`handle`	Yes	Account handle without @, e.g. realDonaldTrump
`replies`	No	Include the account's replies: true or false (default false)

Output Schema

Name	Required	Description	Default
No arguments

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?

Beyond the readOnlyHint/openWorldHint annotations it discloses the upstream data source (truthsocial.com's public Mastodon-style API, fetched via a residential proxy), expected latency (~9 s typical, up to 16 s, budget a 30 s timeout), and the billing model ($0.003 USDC per successful call via x402 on Base/Solana/Arc, failed calls free). These are exactly the operational facts an agent needs before committing to a slow, paid call.

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?

What it returns is front-loaded in the first sentence, followed by source, latency and pricing — a sensible priority order with no filler sentences. The single very long first sentence packing every returned field is dense, but each clause carries distinct 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?

With an output schema present, return-value structure need not be spelled out, yet the description still summarizes it; combined with source, latency/timeout guidance and the payment model, nothing material an agent needs to call this 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 description coverage is 100%, so limit, handle and replies are already fully documented in the schema including defaults and the '0 = profile only' convention. The description restates the post cap ('up to 20 newest posts') but adds no syntax, format or edge-case meaning 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?

The description names a specific resource (a Truth Social account) and enumerates exactly what is returned: profile fields (name, followers, following, post count, verified, website, joined) plus up to 20 newest posts with text, time, replies, reposts, likes, media URLs, link card and repost/quote flags. An agent can distinguish this from the Instagram/Pinterest siblings 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 Guidelines4/5

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

It explicitly routes away from this tool for different needs by naming social_pinterest (latest pins) and social_instagram (engagement snapshot), and it states the timing envelope in which a call should be tolerated. It never states when NOT to use this tool on the same platform (e.g., for a different Truth Social surface), so it stops short of full when/when-not guidance.

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?