Skip to main content
Glama

update_adset

Modify an ad set's settings such as budget, bid strategy, frequency caps, and targeting to adjust campaign delivery and performance.

Instructions

Update an ad set with new settings including frequency caps and budgets.

Args:
    adset_id: Meta Ads ad set ID
    name: New ad set name
    frequency_control_specs: Frequency control specs
                             (e.g. [{"event": "IMPRESSIONS", "interval_days": 7, "max_frequency": 3}])
    bid_strategy: Bid strategy. Valid values:
                 - 'LOWEST_COST_WITHOUT_CAP' (recommended) - no bid_amount required
                 - 'LOWEST_COST_WITH_BID_CAP' - REQUIRES bid_amount
                 - 'COST_CAP' - REQUIRES bid_amount
                 - 'LOWEST_COST_WITH_MIN_ROAS' - REQUIRES bid_constraints with roas_average_floor
                 Note: 'LOWEST_COST' is NOT valid - use 'LOWEST_COST_WITHOUT_CAP'.
    bid_amount: Bid amount in cents. Required for LOWEST_COST_WITH_BID_CAP, COST_CAP, TARGET_COST.
               NOT USED by LOWEST_COST_WITH_MIN_ROAS (uses bid_constraints instead).
    bid_constraints: Bid constraints dict. Required for LOWEST_COST_WITH_MIN_ROAS.
                    Use {"roas_average_floor": <value>} where value = target ROAS * 10000.
                    Example: 2.0x ROAS -> {"roas_average_floor": 20000}
    bid_adjustments: Bid multipliers per targeting dimension. Pass-through to Meta.
                    Shape: {"user_groups": {"<dim>": {"<value>": <float>, "default": <float>}}}
                    See create_adset for full docs and dim list.
                    NOTE: Writing requires a Meta app capability that must be allowlisted.
    status: Update ad set status (ACTIVE, PAUSED, etc.)
    targeting: Complete targeting specifications (replaces existing targeting)
    optimization_goal: Conversion optimization goal (e.g., 'LINK_CLICKS', 'CONVERSIONS', 'VALUE')
    daily_budget: Daily budget in account currency (in cents)
    lifetime_budget: Lifetime budget in account currency (in cents)
    is_dynamic_creative: Enable/disable Dynamic Creative for this ad set.
                        WARNING: This field is immutable after ad set creation. Meta's API will
                        return success but silently ignore the change. To change this, create a new ad set.
    start_time: Start time in ISO 8601 format (e.g., '2023-12-01T12:00:00-0800').
               Use with status=ACTIVE to schedule the ad set for future delivery (effective_status will be SCHEDULED until start_time).
    end_time: End time in ISO 8601 format. Required when lifetime_budget is specified.
    dsa_beneficiary: DSA beneficiary for European compliance (person/org that benefits from ads).
                    Required for EU-targeted ad sets along with dsa_payor.
    dsa_payor: DSA payor for European compliance (person/org paying for the ads).
               Required for EU-targeted ad sets along with dsa_beneficiary.
    multi_advertiser_ads: Set to 0 to opt out of Multi-Advertiser Ads, 1 to opt in.
                         This is a TOP-LEVEL ad set parameter — do NOT put it inside the targeting object.
    regional_regulated_categories: List of regional regulated categories for the ad set.
                                   Required for ads targeting regulated regions (Taiwan, Australia, etc.).
                                   Valid values: TAIWAN_FINSERV, TAIWAN_UNIVERSAL, AUSTRALIA_FINSERV,
                                   INDIA_FINSERV, SINGAPORE_UNIVERSAL, THAILAND_UNIVERSAL.
                                   Set to null/empty to remove existing categories.
    regional_regulation_identities: Dict of verified identity IDs for regional transparency compliance.
                                    Required when regional_regulated_categories is set.
                                    Set individual keys to null to remove them.
    attribution_spec: Attribution window specification for the ad set.
                     WARNING: Meta no longer supports updating attribution_spec after ad set creation
                     (error 1504040). To change attribution windows, create a new ad set instead.
                     This parameter is kept for compatibility but will be rejected by Meta's API.
                     Valid event_type values: CLICK_THROUGH, VIEW_THROUGH.
                     Valid window_days values: 1, 7, 28 (depends on event_type and optimization_goal).
    access_token: Meta API access token (optional - will use cached token if not provided)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adset_idYes
frequency_control_specsNo
bid_strategyNo
bid_amountNo
bid_constraintsNo
bid_adjustmentsNo
nameNo
statusNo
targetingNo
optimization_goalNo
daily_budgetNo
lifetime_budgetNo
is_dynamic_creativeNo
start_timeNo
end_timeNo
dsa_beneficiaryNo
dsa_payorNo
multi_advertiser_adsNo
regional_regulated_categoriesNo
regional_regulation_identitiesNo
attribution_specNo
access_tokenNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Since no annotations are provided, the description carries full burden. It discloses that the tool modifies an existing ad set, includes immutability warnings (Meta silently ignores changes to is_dynamic_creative), and notes permission requirements (Meta app capability for bid_adjustments). It also explains behavior for start_time (SCHEDULED status).

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

Conciseness3/5

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

The description is long (~60 lines) and well-structured with an Args list, but it is verbose. Some redundancy exists (e.g., bid strategy details repeated slightly). However, it front-loads the purpose and uses clear formatting.

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

Completeness5/5

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

Given the 22 parameters and presence of an output schema, the description covers all parameters with explanations, dependencies, warnings, and examples. It addresses complex interactions and edge cases, making it highly complete for a complex tool.

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?

With 0% schema description coverage, the description compensates fully by explaining each parameter in detail: valid values, required combinations, examples, shape, and notes. For instance, it details bid strategy options and their required accompanying parameters.

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 starts with a clear verb and resource: 'Update an ad set with new settings including frequency caps and budgets.' It distinguishes itself from sibling tools like create_adset (creation) and get_adset_details (read) implicitly through its focus on updating existing 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 Guidelines5/5

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

The description provides extensive guidance on when to use this tool, including parameter dependencies (e.g., bid strategy requirements), warnings about immutable fields (is_dynamic_creative, attribution_spec), and when to create a new ad set instead. It also explains optional parameters like access_token.

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