AdSpendSpy for Meta Ad Library

Bring Meta Ad Library research into your AI.

Without signing in, four read-only tools (search_advertisers, get_advertiser_ads, find_similar_advertisers, compare_advertisers) show public advertiser data with a small daily limit. All other tools read your own AdSpendSpy account; your AI asks you to sign in with OAuth the first time you use one.

What you can ask

Rank landing pages by estimated spend and break one down: sections, offer, proof, calls to action and the ad hooks that send traffic to it. No build.
Example path

MCP connector

Server URL: https://www.adspendspy.com/mcp
Login: API key
Protocol: MCP 2026-07-28
Instructions: AdSpendSpy MCP reads your own AdSpendSpy account: tracked advertisers, their ads, saved lists, projects, alerts and AdSpendSpy spend estimates (estimates by AdSpendSpy, not figures reported by Meta). Find an advertiser with or , use its string page_id with , then pass internal_ad_id as .ad_id. Estimated spend is cumulative EUR; timeframe is only a last-seen filter. Each executed authenticated tool consumes one API request; discovery and initialization do not. Prompts rebuild_landing_page and landing_page_teardown guide landing-page research and rebuilds; prompts never consume quota. , , and work without signing in (one call per day, then sign up on adspendspy.com): they show tracked brands' top ads and a 30-day spend range. With a paid plan can also look up an untracked brand live in the Meta Ad Library. Every other tool reads the user's own AdSpendSpy account and asks them to sign in. To research a new advertiser, explicitly add its known page_id and brand_name with first. This changes the account and uses a normal tracked-brand slot. Check remaining_slots; imports run in the background and ads may not be ready yet. All ad reads require active tracking, including saved ads. Removal is available only on the AdSpendSpy website, never through MCP. All other tools are read-only.

Tools

Reads data16

Changes data1

Skills

None in the store listings or on the server

What you can ask

Rank landing pages by estimated spend and break one down: sections, offer, proof, calls to action and the ad hooks that send traffic to it. No build.

Example path

MCP connector

Server URL

https://www.adspendspy.com/mcp

API key

Protocol

MCP 2026-07-28

Instructions

AdSpendSpy MCP reads your own AdSpendSpy account: tracked advertisers, their ads, saved lists, projects, alerts and AdSpendSpy spend estimates (estimates by AdSpendSpy, not figures reported by Meta). Find an advertiser with or , use its string page_id with , then pass internal_ad_id as .ad_id. Estimated spend is cumulative EUR; timeframe is only a last-seen filter. Each executed authenticated tool consumes one API request; discovery and initialization do not. Prompts rebuild_landing_page and landing_page_teardown guide landing-page research and rebuilds; prompts never consume quota. , , and work without signing in (one call per day, then sign up on adspendspy.com): they show tracked brands' top ads and a 30-day spend range. With a paid plan can also look up an untracked brand live in the Meta Ad Library. Every other tool reads the user's own AdSpendSpy account and asks them to sign in. To research a new advertiser, explicitly add its known page_id and brand_name with first. This changes the account and uses a normal tracked-brand slot. Check remaining_slots; imports run in the background and ads may not be ready yet. All ad reads require active tracking, including saved ads. Removal is available only on the AdSpendSpy website, never through MCP. All other tools are read-only.

Tools