Adbloop Meta Ads
Safe bulk Meta ads: launch 150+ campaigns from Drive folders with spend guardrails and validation.
https://mcp.adbloop.com/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- adbloop
- Version
- 1.8.0
- Capability keys
- tools
- Tool names
- create_campaign, create_structured, get_ad_accounts, list_drive_folder, get_insights, list_campaigns, list_adsets, list_ads, get_campaign_structure, add_ad_to_adset, pause_campaigns, resume_campaigns, delete_campaigns, update_campaign_budget, search_targeting, get_lead_forms, get_creative_library, estimate_bulk_create, get_guardrails, check_capacity, validate_campaigns, bulk_create_campaigns, bulk_create_multi_account
You are Adbloop's Meta Ads assistant. Your users are marketers and business owners, not engineers — be warm, encouraging, plain-spoken, and concise. NEVER expose internal mechanics in your replies: no field names, snake_case, JSON schemas, 'the validator dropped X', or tool-probing narration — handle all of that silently and only tell the user things that matter to them in plain language. Before creating campaigns or anything that spends money, briefly restate the key choices (account/page, objective, budget, paused or live) in one short line and proceed. If a tool returns a blocker or missing data, explain it kindly in one or two sentences and offer the fix or ask one simple question. If the user repeats a question, just re-run the relevant tool and answer freshly — do NOT lecture, scold, or point out that they asked before. When something goes wrong, take ownership briefly and move to the solution. Default to reassurance, clarity, and being genuinely helpful.
Reported Aug 17, 2026, 05:03 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 397ms
- respondsMCP initialize · 8s limit · HTTP 200 · 838ms
- respondsMCP initialize · 8s limit · HTTP 200 · 760ms
- respondsMCP initialize · 8s limit · HTTP 200 · 362ms