SiteCheck Shop & Social

Threads profile: name, verified flag, bio, follower count

social_threads_profile

Read-only

Threads (Meta) profile: name, verified flag, bio, follower count and bio links, plus the latest posts the public profile page shows (about 10, including the author's own thread continuations) with text, time, likes, replies, reposts, quotes, media URLs and link. From threads.net through a residential proxy; logged-out pages show a limited number of posts. Related tools on this server, for a different need: social_threads_replies when you need replies to a Threads post: the post itself and the replies; social_threads_search when you need Threads post search: the top posts for a keyword or hashtag. 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": {
      "handle": "<handle>"
    },
    "name": "social_threads_profile"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many posts, 0 to 20 (default 10)
`handle`	Yes	Threads username without @, e.g. zuck

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description discloses the data source and access path (threads.net via residential proxy), a real limitation (logged-out pages expose only a limited number of posts, roughly 10, including the author's own thread continuations), and the cost model ($0.002 USDC per successful call via x402; failures not charged). This is exactly the operational context annotations do not carry.

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 resource and payload, then limitations, then sibling routing, then pricing — a sensible order. The single long field-list sentence is dense but each clause carries information; minor redundancy comes from restating the field list already implied by the title.

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?

Covers the source, the payload, the logged-out post-count caveat, sibling alternatives, and billing — more than enough for a two-parameter read-only scraper. An output schema exists, so the description is not obligated to explain return values, yet it sketches them helpfully.

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%, so both the handle format (no @) and the limit range (0-20, default 10) are already documented in the schema. The description only loosely reinforces this by saying 'about 10' posts are shown; it adds no format, boundary, or interaction semantics beyond that, 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 verb+resource (fetch a Threads/Meta public profile) and enumerates the fields returned: name, verified flag, bio, follower count, bio links, plus the latest ~10 posts with engagement metrics and media URLs. It explicitly names the two closest siblings, social_threads_replies and social_threads_search, so an agent can distinguish 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?

Provides explicit routing: use this tool for profile data, use social_threads_replies when replies to a post are needed, use social_threads_search for keyword/hashtag post search. Each alternative is tied to the condition that selects it, leaving little to inference.

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?