Nexscope Ecommerce Data MCP

Threads Posts

social_threads_user_posts

Read-only

Fetches the most recent posts from a Threads user, returning id, caption text, code, like_count, reshare_count, direct_reply_count, repost_count, image_versions2, video_versions, and taken_at. Only the last 20-30 posts are publicly visible. Supports a trim option for lighter responses. Completed lookups cost at least 10 Nexscope credits. Actual cost depends on the operation and requested options. Repeated requests may purchase data again. Threads Posts API View Pricing Get a user's public Threads posts, limited to roughly the latest 20–30 posts. 1 credit per request Actual supplier units are reported per request. Examples are not guaranteed prices.

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_user_posts"
  }
}

Input Schema

Name	Required	Description	Default
`trim`	No	Set to true for a trimmed down version of the response
`handle`	Yes	Threads username

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

C2.9/5.0

Behavior3/5

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

The description surfaces genuinely useful behavior beyond the readOnly/openWorld/non-destructive annotations: the 20-30 post visibility ceiling and the credit cost model. However, the cost statement is self-contradictory ("at least 10 Nexscope credits" versus "1 credit per request"), which leaves the agent unsure of the real price of a call, and no pagination or rate-limit behavior is described.

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

Conciseness2/5

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

The entry is front-loaded well but bloated by duplicated content: the 20-30 post limit is stated twice, and a scraped pricing block ("Threads Posts API View Pricing Get a user's public Threads posts... 1 credit per request ... Examples are not guaranteed prices") is pasted verbatim at the end. That boilerplate dilutes the actionable information and introduces the credit-count conflict.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read with no output schema, the description covers the essentials: what is returned, the hard visibility cap, and cost awareness. It falls short on how to choose this tool over the other Threads endpoints and on whether the 20-30 results are fixed or can be extended.

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% and both parameters are already documented (handle = Threads username, trim = trimmed response), so the description adds essentially nothing new. The phrase "lighter responses" restates the schema's trim definition rather than clarifying what is dropped or how much smaller the payload becomes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource ("Fetches the most recent posts from a Threads user") and enumerates the returned fields, so the agent knows exactly what it gets. It does not, however, distinguish itself from near-siblings like social_threads_profile, social_threads_post, or social_threads_search, leaving the agent to guess which Threads tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative. The only conditional hint is "Supports a trim option for lighter responses," which helps with parameter choice but says nothing about tool selection among the many Threads siblings.

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

All Nexscope Ecommerce Data MCP 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?