Social Data
Facebook Ad Library Company Ads MCP
Use Facebook Ad Library Company Ads in your AI assistant to retrieve the available information. Explore supported inputs and use cases below.
Facebook Ad Library Company Ads 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 Company Ads
Prompt: Retrieve Facebook Ad Library Company Ads for [page id]. 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. Collect A Bounded Set Of Results
Prompt: Retrieve Facebook Ad Library Company Ads for [page id] across at most two pages within my approved credit budget. Use only the continuation information actually returned, with the same query and filters. Stop at the documented page limit, an absent continuation, an end indicator or a repeated page. Keep source references and report that the collection is bounded, not exhaustive.
3. Focus The Review On A Selected Period
Prompt: Retrieve Facebook Ad Library Company Ads for [page id] for [a period supported by this tool]. Use the documented date meaning, format and limits, and show that scope with the results. Keep required date pairs together. Do not treat a search-index window as an exact publication-time filter or infer a complete historical archive.
4. Prioritize Results For Review
Prompt: Retrieve Facebook Ad Library Company Ads for [page id] using [my preferred documented sort order]. Preserve the source order and identify pinned or promoted items if the response labels them. Do not infer a platform-wide ranking from this returned sample.
5. Build A Focused Shortlist
Prompt: Retrieve Facebook Ad Library Company Ads for [page id], narrowed by [my choices among this tool’s documented filters]. Apply only supported options and combinations, retain the selected scope with the returned items, and do not invent missing classifications, currency or units.
6. Research From A Selected Market Or Request Location
Prompt: Retrieve Facebook Ad Library Company Ads for [page id] using [a supported region or country choice]. Follow this tool’s documented meaning: a request or proxy location is not proof that every result originated there. Report any documented regional coverage limitations with the results.
7. Review Language-Specific Results
Prompt: Retrieve Facebook Ad Library Company Ads for [page id] with [a supported language choice]. Follow the documented language option and report unavailable language-specific content. Do not fabricate a translation or claim that the option guarantees the language of every result.
8. Prepare A Snapshot Of Returned Public Counts
Prompt: Retrieve Facebook Ad Library Company Ads for [page id] 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.
9. Create A Brief From Returned Text
Prompt: Retrieve Facebook Ad Library Company Ads for [page id] 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_facebook_ad_library_company_adshttps://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-company-ads-1",
"method": "tools/call",
"params": {
"name": "social_facebook_ad_library_company_ads",
"arguments": {
"companyName": "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 |
|---|---|---|---|
companyName | string | optional | The name of the company. Can either use this or pageId |
country | string | optional | This can only be one country. It has to be the 2 letter code for the country. It defaults to ALL. |
cursor | string | optional | Cursor to paginate through results |
end_date | string | optional | End date to search for. Format: YYYY-MM-DD |
language | string | optional | Language to filter ads on. Needs to be 2 letter language code, ie EN, ES, FR, etc |
media_type | string | optional | Media type of the ad. Defaults to ALL. Meme refers to ads with image and text. Not sure why they call it meme. Allowed: ALL, IMAGE, VIDEO, MEME, IMAGE_AND_MEME, NONE |
pageId | string | optional | The companies ad library page id. You can get this with my Search For Companies Endpoint. Can either use this or companyName |
sort_by | string | optional | Sort by impressions (high to low), or Most Recent (relevancy_monthly_grouped). Defaults to impressions. Allowed: total_impressions, relevancy_monthly_grouped |
start_date | string | optional | Start date to search for. Format: YYYY-MM-DD |
status | string | optional | Status of the ad. Defaults to ACTIVE. Allowed: ALL, ACTIVE, INACTIVE |
trim | boolean | optional | Set to true for a trimmed down version of the response |
Any of option 1 — requires pageId
Any of option 2 — requires companyName
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 Company Ads for [page id]. 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.