meta-ads-mcp

Overview Schema Source Related Servers Discussions Admin

create_campaign

Create advertising campaigns on Meta Ads with outcome-based objectives, budgets, bid strategies, status, and A/B testing configurations.

Instructions

Create a new campaign in a Meta Ads account.

Note: Campaigns do not support start_time for scheduling — set start_time on the ad set instead.

Args:
    account_id: Meta Ads account ID (format: act_XXXXXXXXX)
    name: Campaign name
    objective: Campaign objective (ODAX, outcome-based). Must be one of:
               OUTCOME_AWARENESS, OUTCOME_TRAFFIC, OUTCOME_ENGAGEMENT,
               OUTCOME_LEADS, OUTCOME_SALES, OUTCOME_APP_PROMOTION.
               Note: Legacy objectives like BRAND_AWARENESS, LINK_CLICKS,
               CONVERSIONS, APP_INSTALLS, etc. are not valid for new
               campaigns and will cause a 400 error. Use the outcome-based
               values above (e.g., BRAND_AWARENESS → OUTCOME_AWARENESS).
    access_token: Meta API access token (optional - will use cached token if not provided)
    status: Initial campaign status (default: PAUSED)
    special_ad_categories: List of special ad categories if applicable
    daily_budget: Daily budget in account currency (in cents) as a string (only used if use_adset_level_budgets=False)
    lifetime_budget: Lifetime budget in account currency (in cents) as a string (only used if use_adset_level_budgets=False)
    buying_type: Buying type (e.g., 'AUCTION')
    bid_strategy: Bid strategy (default: LOWEST_COST_WITHOUT_CAP). Must be one of: 'LOWEST_COST_WITHOUT_CAP', 'LOWEST_COST_WITH_BID_CAP', 'COST_CAP', 'LOWEST_COST_WITH_MIN_ROAS'. WARNING: If you use LOWEST_COST_WITH_BID_CAP or COST_CAP, all child ad sets will require bid_amount to be set.
    bid_cap: Bid cap in account currency (in cents) as a string
    spend_cap: Spending limit for the campaign in account currency (in cents) as a string
    campaign_budget_optimization: Whether to enable campaign budget optimization (only used if use_adset_level_budgets=False)
    ab_test_control_setups: Settings for A/B testing (e.g., [{"name":"Creative A", "ad_format":"SINGLE_IMAGE"}])
    use_adset_level_budgets: If True, budgets will be set at the ad set level instead of campaign level (default: False)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "account_id": "<account_id>",
      "name": "<name>",
      "objective": "<objective>"
    },
    "name": "create_campaign"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`status`	No	PAUSED
`bid_cap`	No
`objective`	Yes
`spend_cap`	No
`account_id`	Yes
`buying_type`	No
`access_token`	No
`bid_strategy`	No	LOWEST_COST_WITHOUT_CAP
`daily_budget`	No
`lifetime_budget`	No
`special_ad_categories`	No
`ab_test_control_setups`	No
`use_adset_level_budgets`	No
`campaign_budget_optimization`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.77Aug 17, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full behavioral burden. It discloses important traits: campaigns don't support start_time, legacy objectives cause a 400 error, bid strategy implications for child ad sets, and budget placement behavior via use_adset_level_budgets. It also mentions token caching. However, it doesn't describe return values or side effects beyond creation, leaving some gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized for 15 parameters, with a clear structure: purpose, important note, then a parameter list. It's front-loaded with the primary action. Some entries could be more compact (e.g., repeated 'in account currency (in cents) as a string'), but overall every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of 15 parameters and the absence of annotations, the description covers key behavioral warnings, parameter interdependencies, and default values. It doesn't explain the return value (though an output schema exists) or explicitly compare to sibling tools for when to use this vs create_adset, but it's largely complete for a create operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description fully compensates. Every parameter is explained with formats (e.g., act_XXXXXXXXX), allowed values (objective and bid_strategy enums), defaults, and conditional usage (e.g., budgets only used when use_adset_level_budgets=False). This goes well beyond the bare schema and adds critical warnings.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Create a new campaign in a Meta Ads account,' which clearly states the verb (create) and resource (campaign in a Meta Ads account). It also adds a critical distinction from sibling tools like create_adset and create_ad by specifying it's for campaigns specifically and notes that start_time belongs on ad sets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While it doesn't explicitly say 'use this instead of X,' it provides clear context about campaign creation, including the account_id format and objective requirements. The note about start_time implicitly guides users to create ad sets for scheduling, which offers some usage guidance without naming alternatives directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.