mcp-meta-ad-library-monitor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_meta_adsA | Search the Meta Ad Library for a company's ads through Facebook's sanctioned Graph API and return ONE FLAT ROW PER AD with creative text, headline, delivery dates, the Meta surfaces it ran on and Meta's permanent snapshot URL for the rendered ad. COVERAGE IS NOT UNIVERSAL: the Ad Library holds all ads only in the EU and only political and issue ads elsewhere, so a commercial advertiser outside the EU is legitimately absent and every row carries a coverage note saying what the search could have found. Requires the caller's own Meta app access token, as the metaAccessToken argument or the META_ACCESS_TOKEN environment variable. Use it to check whether a company advertises on Facebook and Instagram right now or to pull a creative history; each call is a point in time read, so monitoring means calling it on a schedule and comparing rows. Not for organic posts or follower counts, which the brand presence mappers cover. Impressions and spend exist for political ads only and arrive as bands, so a null there is not zero spend. Read only; requires an APIFY_TOKEN and consumes Apify credits per call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With a single tool there is no possibility of misselection between tools. The description also explicitly bounds the tool's scope (paid Meta ads only, read-only, not organic posts or follower counts), so its boundary against adjacent capabilities is clear.
The lone name 'find_meta_ads' follows a clean verb_noun snake_case convention that matches the domain vocabulary. Nothing in the set deviates from that pattern.
A single tool is thin for a server explicitly framed as an ad 'monitor', which implies repeated reads, comparison, or advertiser discovery. It does one job well, but the surface feels minimal relative to the stated purpose.
Read-only search is the right shape for the public Ad Library, and the one tool covers the primary advertiser lookup. However, there is no way to fetch a specific ad by ID or snapshot, no advertiser/keyword discovery, and no pagination or multi-company batch, leaving notable gaps for monitoring workflows.