Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/kubachour/mobile-growth-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/kubachour/mobile-growth-mcp/meta-api-tools)<a href="https://agentmods.dev/rules/kubachour/mobile-growth-mcp/meta-api-tools"><img src="https://agentmods.dev/badge/rules/kubachour/mobile-growth-mcp/meta-api-tools.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.00707 |
| Opus 5 | $0.00011 | $0.00353 |
| Sonnet 5 | $0.00004 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
meta-api-tools scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Meta Marketing API Tools
When the user asks about their Meta ad account data, use the MCP tools. All tools require ad_account_id (e.g. act_123456789).
Rate Limit Safety
- All tools default to
last_7d, active-only, minimal fields - No auto-pagination — returns first page + cursor for explicit next page
- Throttle header monitored — warns at >75% utilization
- If rate limited, wait and retry. Don't make unnecessary calls.
Tool Reference
get_meta_campaigns
get_meta_campaigns(ad_account_id="act_XXX")
Returns: id, name, status, objective, bid_strategy, budgets. Optional: fields, effective_status, limit, after.
get_meta_adsets
get_meta_adsets(ad_account_id="act_XXX", campaign_id="optional")
Returns: id, name, status, campaign_id, optimization_goal, bid_strategy, targeting. Optional: fields, effective_status, limit, after.
get_meta_ads
get_meta_ads(ad_account_id="act_XXX", adset_id="optional")
Returns: id, name, status, adset_id, creative info. Optional: fields, effective_status, limit, after.
get_meta_insights
The most flexible tool. Configurable level, breakdowns, date range.
get_meta_insights(
ad_account_id="act_XXX",
level="campaign", # account | campaign | adset | ad
date_preset="last_7d", # or time_range={since, until}
time_increment="1", # "1" daily, "7" weekly, omit for aggregated
breakdowns="age,gender", # or "publisher_platform,platform_position"
conversion_event="mobile_app_install",
sort="spend_descending",
limit=50
)
get_meta_ad_fatigue
Built-in fatigue detection. Single API call.
get_meta_ad_fatigue(
ad_account_id="act_XXX",
campaign_id="optional",
frequency_warning=3,
frequency_critical=5,
ctr_decline_threshold=30
)
Common Patterns
Campaign overview: get_meta_campaigns → get_meta_insights at campaign level
Deep dive on one campaign: get_meta_adsets(campaign_id=X) → get_meta_insights(level="ad") filtered to that campaign
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 82 lines · 22 tokens per session scan A 47850103c52a
meta-api-tools is a cursor rule published in the GitHub repository kubachour/mobile-growth-mcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 707 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.