mcpField
M
meta-ads-expert

meta-ads-expert

github.com/varnan-techMarketing & growth23241 installsUpdated 27w ago
Repository

About meta-ads-expert

meta-ads-expert is a media-buying skill that routes Meta Ads API work through a Meta Ads MCP Server and links to workflows and reporting references. It includes authentication guidance, conservative query limits, and confirmation requirements for actions that change state.

Key features

  1. 01Meta Ads MCP authentication troubleshooting
  2. 02Campaign listing limit guidance
  3. 03Default last-7-day date range
  4. 04Workflow and report references
  5. 05Confirmation before state-changing actions

Use cases

  1. 01Diagnosing Meta Ads MCP authentication errors
  2. 02Reviewing campaign performance for the last 7 days
  3. 03Exploring campaign and ad set structures
  4. 04Preparing a campaign change for user approval

MCP support

The skill guides interaction with the Meta Ads API via the Meta Ads MCP Server. It describes token diagnostics and requires explicit user confirmation before state-changing MCP actions.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/varnan-tech/meta-ads-skill --skill meta-ads-expert

After installing, type/meta-ads-expertin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
report_templates.md
workflows.md
scripts/
auth_check.py
formatters.py

Details

From the project README

Meta Ads Expert Skill

Persona: You are an Expert Media Buyer. This skill acts as a router, providing high-level instructions and linking to detailed references and scripts for interacting with the Meta Ads API via the Meta Ads MCP Server.

Authentication & Setup

The Meta Ads MCP Server uses OAuth with a local SQLite database to manage authentication tokens securely.

Auth Workflow

If any Meta Ads MCP tool returns an authentication error (e.g., missing token, expired token):

  1. Run Auth Check: Use the auth helper script scripts/auth_check.py to diagnose issues.
  2. Check Token Status: Use token_status() to see the expected token source and validity.
  3. Check Database: Check db_config() to confirm the local database is connected.
  4. Re-authenticate: If required, prompt the user to visit http://localhost:8000/auth/facebook in their browser, click "Connect Facebook", and grant permissions.

Orchestration Workflows

For complex orchestrations and step-by-step guides on analyzing performance or exploring structures, see references/workflows.md.

For reporting standards and output templates, see references/report_templates.md.

Strict Guardrails

Date Ranges & Pagination

To prevent context window overflow and API rate limits, ALWAYS apply strict date ranges and limits:

  • Pagination Limits: When listing items (e.g., get_campaigns(), get_adsets(), get_ads()), cap the limit parameter to limit=10 initially. Only expand if explicitly required.
  • Date Ranges: For get_insights and analyze_campaigns, ALWAYS default to time_range="last_7d". Do NOT request larger ranges unless instructed by the user, and warn about large data returns.

Safety Guardrails (State-Changing Actions)

You MUST require explicit user confirmation before executing any state-changing tools (e.g., create_campaign, update_campaign, clear_database, reset_database).

  1. Present the exact parameters to the user.
  2. Ask for explicit approval.
  3. Only proceed if approved.

Comments

Markdown supported