Skip to main content
Glama

update_campaign

Modify campaign name, status, budgets, bid strategy, and migrate from CBO to ABO by providing ad set budgets.

Instructions

Update an existing campaign in a Meta Ads account.

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

Migrating CBO (Advantage Campaign Budget) → ABO (ad set level budgets):
    Pass `adset_budgets` with one entry per ad set in the campaign. Meta atomically
    removes the campaign-level budget and assigns budgets at the ad set level in a
    single call. This is Meta's documented mechanism — the legacy
    `use_adset_level_budgets=true` flag attempts to clear `daily_budget`/`lifetime_budget`
    but Meta silently ignores the empty values, so the migration does not persist.

Args:
    campaign_id: Meta Ads campaign ID
    access_token: Meta API access token (optional - will use cached token if not provided)
    name: New campaign name
    status: New campaign status (e.g., 'ACTIVE', 'PAUSED')
    special_ad_categories: List of special ad categories if applicable
    daily_budget: New daily budget in account currency (in cents).
    lifetime_budget: New lifetime budget in account currency (in cents).
    bid_strategy: New bid strategy
    bid_cap: New bid cap in account currency (in cents) as a string
    spend_cap: New spending limit for the campaign in account currency (in cents) as a string
    campaign_budget_optimization: Enable/disable campaign budget optimization
    objective: New campaign objective (Note: May not always be updatable)
    use_adset_level_budgets: Deprecated for CBO → ABO migration — use `adset_budgets`
        instead. Kept for backwards compatibility; sends empty `daily_budget`/
        `lifetime_budget` which Meta silently ignores in most cases.
    adset_budgets: List of `{"adset_id": "...", "daily_budget": <cents>}` objects.
        Use to migrate from CBO to ABO: Meta removes the campaign-level Advantage
        budget and assigns the provided daily budgets at the ad set level in one
        atomic call. Example:
            [{"adset_id": "1234", "daily_budget": 5000},
             {"adset_id": "5678", "daily_budget": 7000}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes
access_tokenNo
nameNo
statusNo
special_ad_categoriesNo
daily_budgetNo
lifetime_budgetNo
bid_strategyNo
bid_capNo
spend_capNo
campaign_budget_optimizationNo
objectiveNo
use_adset_level_budgetsNo
adset_budgetsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that `use_adset_level_budgets` is deprecated and its behavior is unsupported (Meta silently ignores empty values). It also explains the atomic migration via `adset_budgets`. However, it does not describe auth requirements beyond `access_token` (optional with cached token), rate limits, or what happens if conflicting parameters are provided.

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 fairly long but well-structured with a note, a migration section, and an Args list. Every sentence adds value, though some redundancy exists (e.g., repeating example in migration section and Args). Could be slightly more streamlined without losing clarity.

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 tool's complexity (14 parameters, 0% schema coverage, no annotations), the description covers most aspects: parameter explanations, migration caveats, deprecated flags. The output schema exists, so return values aren't needed. However, it lacks information on error scenarios, idempotency, or interactions between parameters (e.g., setting both `daily_budget` and `adset_budgets`).

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 description coverage is 0%, so the description must compensate. It does so comprehensively: each parameter is listed with type, unit (cents for budgets, string for bid_cap), and special notes (e.g., `objective` may not be updatable, `adset_budgets` is a list of objects with example). This adds essential meaning beyond the raw schema.

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 begins with a clear verb+resource: 'Update an existing campaign in a Meta Ads account.' This distinguishes the tool from sibling tools like create_campaign, and is specific enough to avoid confusion with update_adset or update_ad.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance, especially around CBO→ABO migration: it explains the correct method using `adset_budgets` and warns against the deprecated `use_adset_level_budgets`. It also notes that `start_time` should be set on ad sets, not campaigns, and that `objective` may not always be updatable. This helps the agent choose correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pipeboard-co/meta-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server