SiteCheck Shop & Social

Replies to a Threads post: the post itself and the replies

social_threads_replies

Read-only

Replies to a Threads post: the post itself (text, likes, reply/repost/quote counts) and the replies the public post page shows (first page, typically 10-25, including short reply chains and the author's own thread continuations) with author, text, time, likes and who each reply answers. From threads.net through a residential proxy. Related tools on this server, for a different need: social_threads_search when you need Threads post search: the top posts for a keyword or hashtag; social_threads_profile when you need Threads profile: name, verified flag, bio, follower count. 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": {
      "url": "<url>"
    },
    "name": "social_threads_replies"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Threads post URL (threads.net or threads.com), or a bare post code such as DeZtp-TkQHh together with handle
`limit`	No	How many replies, 1 to 50 (default 20)
`handle`	No	Author username, only needed when url is a bare post code

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/openWorldHint it discloses non-obvious behavior: only the first page is returned (typically 10-25 replies, including short reply chains and the author's own thread continuations), the data is fetched from threads.net through a residential proxy, and billing is $0.002 USDC per successful call via x402 with failed calls not charged. The cost and no-charge-on-failure semantics are things no annotation or schema conveys.

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?

The core capability and its scope are front-loaded in the first clause, and the pricing/proxy sentence is genuinely useful. However, the scaffolding phrase "Related tools on this server, for a different need" and repeated restatement of each sibling's payload add bulk that could be tightened without losing routing 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?

For a read-only scraping tool with three parameters and an output schema, the description covers everything an agent needs: what is returned, how deep the coverage goes, the transport/proxy path, and the per-call cost with failure billing rules. Nothing material is left to inference.

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 url, limit and handle are already fully documented, making 3 the baseline. The description adds indirect meaning about depth ("first page, typically 10-25") and lists returned reply fields, but it never explicitly states that raising limit beyond the visible page yields little, nor does it clarify the bare-post-code plus handle combination beyond what the schema says.

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 verb and resource ("Replies to a Threads post") and enumerates exactly what comes back: the post itself with text, likes and reply/repost/quote counts, plus the replies the public page shows with author, text, time, likes and reply targets. It also explicitly separates itself from social_threads_search (keyword/hashtag post search) and social_threads_profile (profile metadata), so an agent can pick correctly 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 provides explicit routing: use this for replies to a known post, use social_threads_search "when you need Threads post search: the top posts for a keyword or hashtag," and social_threads_profile "when you need Threads profile." Each alternative is paired with the condition that selects it, which is the strongest form of when-to-use 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?