All About Ads MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_API_TOKEN | Yes | Your Apify API token. Get a free token at https://apify.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_facebook_adsA | Search the Facebook Ads Library for live ads matching the given queries. Runs a remote scraper (30s–few minutes). Full results are saved to a JSON file; only a compact preview is returned inline. Use read_saved_results to page through the full dataset without flooding context. |
| search_instagram_profilesA | Fetch public Instagram profile data including follower counts, bio, and recent posts. Runs a remote scraper (30s–few minutes). Full results are saved to a JSON file; only a compact preview is returned inline. Use read_saved_results to page through the full dataset without flooding context. |
| search_google_adsA | Search the Google Ads Transparency Center for live ads by advertiser name or domain. Returns headlines, formats, regions, days_active, and destination URLs. Runs a remote scraper (30s–few minutes). Full results are saved to a JSON file; only a compact preview is returned inline. Use read_saved_results to page through the full dataset without flooding context. |
| search_googleA | Search Google for organic results to research brands, news, and ad context. Runs a remote scraper (30s–few minutes). Full results are saved to a JSON file; only a compact preview is returned inline. Use read_saved_results to page through the full dataset without flooding context. |
| list_saved_resultsA | List all result files saved from previous scraper runs. Returns one entry per file with path, size, item count, tool name, and queries. No Apify call is made — this is instant. Use read_saved_results to read items. |
| read_saved_resultsA | Read a paginated slice of items from a previously saved scraper results file. Results files can be very large. Read in small pages and project only the fields you need to stay within context limits. |
| start_facebook_ads_scrapeA | Start a Facebook Ads Library scrape in the background and return a run_id immediately. Use this instead of search_facebook_ads when running multiple scrapers in parallel. Call check_run_status to monitor progress, then collect_scrape_results once SUCCEEDED. |
| start_google_ads_scrapeA | Start a Google Ads Transparency Center scrape in the background and return a run_id immediately. Use this instead of search_google_ads when running multiple scrapers in parallel. Call check_run_status to monitor progress, then collect_scrape_results once SUCCEEDED. |
| start_instagram_scrapeA | Start an Instagram profile scrape in the background and return a run_id immediately. Use this instead of search_instagram_profiles when running multiple scrapers in parallel. Call check_run_status to monitor progress, then collect_scrape_results once SUCCEEDED. |
| check_run_statusA | Check the current status of one or more background Apify scrape runs. Returns done and succeeded flags for each run so you know when to call collect_scrape_results. |
| collect_scrape_resultsA | Collect and save results from a completed background Apify scrape run. The run must have SUCCEEDED — check with check_run_status first. Results are saved to a file and a compact preview is returned inline, identical to the blocking search_* tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| about | Overview of the all-about-ads MCP server and its capabilities. |
TDQS
Scored across 11 tools
Each tool has a clearly distinct purpose: managing background runs, retrieving results, or searching specific ad platforms. The blocking vs. async variants are well-differentiated by their names and descriptions.
All tools follow a consistent verb_noun pattern with lowercase underscores (e.g., search_facebook_ads, start_google_ads_scrape, collect_scrape_results). No mixing of conventions.
11 tools cover the essential operations for an ad scraping server: searches (blocking and async) for multiple platforms, status checking, result collection, and saved results management. The count feels well-scoped.
The tool surface covers the full lifecycle of ad scraping—search, async start, status, collect, list, read. Missing are a delete or cancel capability, but these are minor given the domain.