Social Data
Creator Tools Find Social Profiles MCP
Use Creator Tools Find Social Profiles in your AI assistant to retrieve the available information. Explore supported inputs and use cases below.
Creator Tools Find Social Profiles 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 Creator Tools Find Social Profiles
Prompt: Find publicly linked profiles for [supported source platform], [account handle]. Separate verified source-linked profiles from same-handle candidates, and show partial or failed discovery steps. Do not assume matching handles belong to the same person.
2. Review Unverified Same-Handle Candidates
Prompt: Find public profiles associated with [supported platform] and [creator handle]. Separate verified linked profiles from same-handle candidates that lack ownership evidence. Show the returned confidence and evidence without promoting an unverified match to the creator’s identity, and do not contact any account.
3. Audit Gaps In A Creator’S Public Link Map
Prompt: Run one profile discovery for [supported platform] and [creator handle]. Report verified profile links, source-declared websites and failed discovery branches separately so I can decide what needs manual review. A partial result or failed fetch is not proof that another profile does not exist. Do not retry automatically or broaden the crawl.
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_find_social_profileshttps://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-find-social-profiles-1",
"method": "tools/call",
"params": {
"name": "social_find_social_profiles",
"arguments": {
"handle": "creator",
"platform": "instagram"
}
}
}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 |
|---|---|---|---|
platform | string | required | Source social platform Example: instagram |
handle | string | required | Creator handle without a profile URL. A leading @ is optional. Example: creator |
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 (10 credits). [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
Find publicly linked profiles for [supported source platform], [account handle]. Separate verified source-linked profiles from same-handle candidates, and show partial or failed discovery steps. Do not assume matching handles belong to the same person.
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.