Social Data
Facebook Ad Library Search for Companies MCP
Use Facebook Ad Library Search for Companies in your AI assistant to retrieve the available information. Explore supported inputs and use cases below.
Facebook Ad Library Search for Companies 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 Facebook Ad Library Search For Companies
Prompt: Retrieve Facebook Ad Library Search for Companies for [search phrase]. 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. Disambiguate Advertisers With Similar Names
Prompt: Search the Meta Ad Library for [company name]. Compare returned page names, aliases, categories, countries and verification labels so I can identify the intended advertiser page. Keep page IDs attached to each candidate; matching names alone are not proof of common ownership.
3. Map Advertiser Pages To Returned Instagram Accounts
Prompt: Search for [company name] and list each returned Facebook page ID alongside its supplied Instagram username, verification label and follower count. Leave missing Instagram details blank. This maps the library’s returned associations; it does not prove conversion performance or identify every account owned by the company.
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_facebook_ad_library_search_companieshttps://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-facebook-ad-library-search-companies-1",
"method": "tools/call",
"params": {
"name": "social_facebook_ad_library_search_companies",
"arguments": {
"query": "nike"
}
}
}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 |
|---|---|---|---|
query | string | required | Keyword to search for Example: nike |
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 Facebook Ad Library Search for Companies for [search phrase]. 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.