Skip to main content
Glama
swesmith-repos

Meta Ads MCP

update_campaign

Modify an existing Meta Ads campaign's settings including name, status, budget, bid strategy, and objectives to optimize advertising performance.

Instructions

Update an existing campaign in a Meta Ads account.

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) as a string. 
                 Set to empty string "" to remove the daily budget.
    lifetime_budget: New lifetime budget in account currency (in cents) as a string.
                    Set to empty string "" to remove the lifetime budget.
    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: If True, removes campaign-level budgets to switch to ad set level budgets

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations provided, the description carries full burden but provides minimal behavioral context. It states this updates an existing campaign but doesn't disclose important traits: what permissions are needed, whether changes are reversible, rate limits, error conditions, or what happens when partial updates fail. The description mentions 'May not always be updatable' for objective but doesn't explain when or why.

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 a 13-parameter tool. It uses a clear two-part structure: purpose statement followed by parameter documentation. Every sentence adds value, though the parameter section could be more front-loaded with critical information about required vs optional parameters.

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

Completeness3/5

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

Given the complexity (13 parameters, mutation operation, no annotations) and existence of an output schema, the description is partially complete. It excels at parameter semantics but lacks behavioral context and usage guidelines. For a mutation tool with many parameters, it should provide more about error handling, constraints, and typical use cases.

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?

The description provides extensive parameter documentation beyond the 0% schema coverage. It explains 12 parameters with practical details: currency units (cents), special values (empty string to remove budgets), examples (status values like 'ACTIVE'), and behavioral notes (use_adset_level_budgets removes campaign-level budgets). This fully compensates for the lack of schema descriptions.

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

Purpose4/5

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

The description clearly states 'Update an existing campaign in a Meta Ads account' - a specific verb (update) and resource (campaign). It distinguishes from siblings like 'create_campaign' by specifying 'existing campaign', but doesn't explicitly differentiate from other update tools like 'update_ad' or 'update_adset' beyond the resource type.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, constraints, or compare with other campaign-related tools like 'get_campaign_details' for reading or 'create_campaign' for creation. The agent must infer usage from the tool name alone.

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/swesmith-repos/pipeboard-co__meta-ads-mcp.36128861'

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