How do I find my Facebook Ad Account ID?

You can find your Ad Account ID in the **Meta Ads Manager**. It's the numeric ID shown in the URL or account selector. Ensure you provide it without the 'act_' prefix.

Can I pause an underperforming campaign using this agent?

Yes! Use the `update_campaign_status` tool and set the status to `PAUSED`. You can also resume it later by setting it back to `ACTIVE`.

Which performance metrics are available in the insights?

The `get_insights` tool provides comprehensive data including impressions, clicks, total spend, reach, CPC (cost per click), CTR (click-through rate), and CPP (cost per purchase).

Facebook Ads MCP Server for CrewAI 12 tools — connect in under 2 minutes

Name: Facebook Ads
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Facebook Ads through the Vinkius — pass the Edge URL in the `mcps` parameter and every Facebook Ads tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Facebook Ads Specialist",
    goal="Help users interact with Facebook Ads effectively",
    backstory=(
        "You are an expert at leveraging Facebook Ads tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Facebook Ads "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Facebook Ads MCP Server

Connect your Facebook Ads (Meta Marketing) account to any AI agent and take full control of your advertising campaigns through natural conversation.

When paired with CrewAI, Facebook Ads becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Facebook Ads tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Campaign Management — List all campaigns, fetch detailed settings, and update statuses (ACTIVE/PAUSED) directly from the cloud
Ad Set & Ad Inspection — Drill down into specific ad sets and ads to review targeting, budgets, and creative details
Performance Insights — Extract granular metrics like impressions, clicks, spend, reach, and CPC to analyze your ROI
Account Overview — Retrieve ad account metadata including balance, currency, and overall account status
Identity Context — Verify the authorized user and access level for the connected marketing token

The Facebook Ads MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Facebook Ads to CrewAI via MCP

Follow these steps to integrate the Facebook Ads MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 12 tools from Facebook Ads

Why Use CrewAI with the Facebook Ads MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Facebook Ads through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Facebook Ads + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Facebook Ads MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Facebook Ads for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Facebook Ads, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Facebook Ads tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Facebook Ads against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Facebook Ads MCP Tools for CrewAI (12)

These 12 tools become available when you connect Facebook Ads to CrewAI via MCP:

get_ad_account_info

Get basic info for the Facebook Ad Account

get_ad_details

Get details for a specific ad

get_ad_set_details

Get details for a specific ad set

get_campaign_details

Get details for a specific campaign

get_insights

Get performance insights for the Ad Account

get_me

Get current token identity info

list_ad_sets

List ad sets in the Ad Account

list_ads

List ads in the Ad Account

list_campaigns

List campaigns in the Ad Account

update_ad_set_status

Update the status of an ad set

update_ad_status

Update the status of an ad

update_campaign_status

Update the status of a campaign

Example Prompts for Facebook Ads in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Facebook Ads immediately.

"List all active campaigns in my ad account."

"Show me the performance insights for the last week."

"Pause campaign 123456789."

Troubleshooting Facebook Ads MCP Server with CrewAI

Common issues when connecting Facebook Ads to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Facebook Ads + CrewAI FAQ

Common questions about integrating Facebook Ads MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.