7.9
/ 10
1 evaluations
3.5k Downloads
Overview
Provide full read/write programmatic control over Meta (Facebook) Ads accounts, including campaigns, ad sets, ads, creatives, and comprehensive performance insights via the Meta Graph API.
Key Advantages
1.End-to-end coverage of core Meta Ads objects: campaigns, ad sets, ads, and creatives with CRUD (create, read, update, delete) operations.
2.Integrated performance insights at account, campaign, ad set, and ad level, including metrics, breakdowns, date presets, and custom date ranges.
3.Clear environment-variable based configuration (access token, ad account ID) compatible with automated and production workflows.
4.Thorough documentation of objectives, targeting options, budget types, status values, metrics, attribution windows, pagination, and rate limits.
5.Supports both user and system user tokens, with guidance on token extension and debugging, suitable for long-running automations.
Use Cases
- Automating campaign lifecycle management (create, update, pause, delete) for Meta ad campaigns at scale.
- Building internal dashboards or reports that pull multi-level insights (account/campaign/ad set/ad) with breakdowns and date presets.
- Performance-based automation such as pausing underperforming ads/ad sets or reallocating budgets based on spend, CPC, CTR, or conversions.
- Bulk management tools for advertisers or agencies (e.g., mass campaign creation, bulk pausing, or editing budgets).
- Back-end services that maintain always-on Meta campaigns using long-lived or system user tokens with scheduled optimizations.
Evaluation Scores
7.9
/ 10
Reliability
7.8
Functionality
8.8
Usability
8.5
Safety
6.0
Performance
8.0
Compatibility
9.0
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.9/103/19/2026▼
OS: linux-arm64LLM: anthropic/claude-sonnet-4.6
**Quick judgment:** This is a strong, production-oriented Meta (Facebook) Ads integration that exposes most of the practical capabilities needed to manage and analyze ad accounts programmatically. It is best suited for technical users (developers, growth engineers, performance marketers with API familiarity) who want comprehensive control rather than a simplified interface.
**What it does well**
- Covers full CRUD for campaigns, ad sets, ads, and creatives, plus all the key insights endpoints.
- Documentation is unusually thorough: objectives, targeting structures, budgets (in cents), status values, metrics, attribution windows, pagination, and rate limits are all clearly described with concrete curl examples.
- Supports both user and system user tokens, with guidance on extending tokens and debugging them—important for stable, long-running automations.
- Insight queries support breakdowns, date presets, custom date ranges, time increment, and attribution windows, which is enough for most reporting and optimization workflows.
**Key risks / limitations**
- **High blast radius:** Full write access means a misconfigured call could accidentally change budgets, pause/activate large numbers of campaigns, or delete objects. There’s no built-in safety layer (e.g., dry-run mode, budget caps, or confirmation steps), so callers must implement their own guardrails.
- **Token & permission management:** Requires correct token scopes (`ads_read`, `ads_management`) and secure handling of access tokens. Mismanagement can lead to outages or security issues.
- **Rate limits and errors:** The docs explain Meta’s rate limits and recommend exponential backoff, but actual robustness will depend on how the calling workflows implement retries and error handling.
**Recommended scenarios**
- Agencies or advanced advertisers automating campaign management and reporting for multiple clients.
- Back-end services that need to programmatically spin up campaigns/ad sets/ads and then monitor/optimize them via insights.
- Internal analytics or BI pipelines that aggregate Meta performance metrics with breakdowns, without relying on third-party tools.
**Use with caution if** you want non-technical marketers to drive changes directly, you lack strong access-control practices for tokens, or you need additional safety mechanisms to prevent accidental large-scale budget or status changes.
Comments (0)
No comments yet. Be the first!