Social Data
Threads Post MCP
Use Threads Post in your AI assistant to retrieve the available information. Explore supported inputs and use cases below.
Threads Post AI Prompts & Use Cases
After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.
New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.
1. Review Threads Post
Prompt: Retrieve Threads Post for [public URL]. Summarize only the information actually returned and preserve source links when available. Report private, restricted, missing or partial results explicitly; missing values are not zero.
2. Prepare A Snapshot Of Returned Public Counts
Prompt: Retrieve Threads Post for [public URL] and make a compact table of the public counts actually returned. Keep each count attached to its item or account, label estimates and preserve the observation time when supplied. Do not invent engagement rates, historical growth, unique audience size or missing values.
3. Create A Brief From Returned Text
Prompt: Retrieve Threads Post for [public URL] and prepare a brief about [my research question] using only text present in the response. Cite the corresponding source links when returned, distinguish quotations from interpretation, and report insufficient text. Do not claim to have read linked pages or infer private information.
What You Need to Provide
Use only the documented public inputs. Private, restricted, missing and partial results remain distinct; missing metrics are not zero.
Check the current Nexscope price before running the request. Optional enrichment, downloads, transcription and additional pages can incur charges. These examples do not execute a request.
Step 1 · Connect
Connect Your AI Assistant
Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.
POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxUsing an API key? Get your key from API Access and include it in the Authorization header shown above.
Call this MCP tool
social_threads_posthttps://api.nexscope.ai/mcptools/callInitialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.
{
"jsonrpc": "2.0",
"id": "social-threads-post-1",
"method": "tools/call",
"params": {
"name": "social_threads_post",
"arguments": {
"url": "https://www.threads.com/@trendspider/post/DIU8naHS6q_"
}
}
}MCP 2025-11-25 · Streamable HTTPProgress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
url | string | required | The URL of the post to get Example: https://www.threads.com/@trendspider/post/DIU8naHS6q_ |
trim | boolean | optional | Set to true for a trimmed down version of the response |
cache_max_age | string | optional | If we have a response in the cache that is this many days old or newer, return the cached response (0 credits, with "cached": true and a "cached_at" timestamp). Otherwise, scrape a live result (1 credit). [See the Caching page for details.](https://docs.scrapecreators.com/caching) |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
code | integer | required | 0 means accepted or successful; nonzero is a platform error. |
cost | string | required | Elapsed milliseconds, never credits; -1 outside web requests. |
data | any | required | Data value used by this API operation. |
msg | string | null | required | Msg value used by this API operation. |
time | string | required | Server local time: yyyy-MM-dd HH:mm:ss. |
traceId | string | null | required | Trace id value used by this API operation. |
ts | string | required | Epoch milliseconds. |
Any of option 1 — requires platform, resourceStatus, data, usage
| Name | Type | Required | Description |
|---|---|---|---|
data | object | required | Data value used by this API operation. |
data.data | object | required | Data value used by this API operation. |
data.platform | string | required | Platform value used by this API operation. |
data.resourceStatus | string | required | Resource status value used by this API operation. |
data.usage | object | required | Usage value used by this API operation. |
Any of option 2
| Name | Type | Required | Description |
|---|---|---|---|
data | null | required | Data value used by this API operation. |
Workflow Guide
Workflow example, not a verified API response.
Your Goal
Retrieve Threads Post for [public URL]. Summarize only the information actually returned and preserve source links when available. Report private, restricted, missing or partial results explicitly; missing values are not zero.
Suggested Steps
Provide the documented public identifiers or search inputs. The assistant can then make the requested lookup and organize only the returned evidence. Missing or restricted results must be reported explicitly; no actual lookup or returned metrics are claimed here.
About this sample: Workflow example based on the published API document, not a live API response.
Published sample data is not available for this page. A format illustration or workflow guide is not a substitute for a published result.
View the MCP Request & Response Format
Examples
Workflow example, not a verified API response.
The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.
MCP Request
No verified MCP request example is available. Refer to Integration and the documented requirements before preparing a call.
MCP Response Format
This workflow does not claim an API result. No verified response example is available; refer to Parameters & Response for the documented response structure.