Skip to main content
Glama

update_adset

Update an existing Meta ad set with supervised validation and rollback support. Modify name, status, budget (ABO only), targeting (partial updates allowed), or schedule. Enforces ABO/CBO budget rules and verifies post-write state.

Instructions

Update an existing ad set. Supervised write - validates before applying.

Takes a pre-write snapshot for rollback, validates the update payload, applies via Meta API, and verifies post-write state.

Note on budgets: ABO/CBO rules are enforced. If the parent campaign uses CBO (has campaign-level budget), ad set budget updates are blocked. Budget updates are only allowed for ABO ad sets (parent campaign has no budget).

Note on targeting: targeting_json must be a valid Meta targeting spec JSON object. Partial updates are supported - Meta merges provided fields with existing targeting. To clear a field, set it explicitly to null in the JSON.

Args: adset_id: Ad set ID to update. name: New ad set name. Subject to naming enforcement. status: New status. Allowed: 'PAUSED', 'ACTIVE', 'ARCHIVED'. Activating requires confirmation-level validation. daily_budget: New daily budget in currency units (e.g., 15.0 for EUR 15). Only allowed for ABO ad sets. Mutually exclusive with lifetime_budget. lifetime_budget: New lifetime budget in currency units. Only allowed for ABO ad sets. Mutually exclusive with daily_budget. targeting_json: JSON string of targeting spec to apply. Example: '{"geo_locations":{"countries":["GR"]},"age_min":25,"age_max":55}' start_time: New start time (ISO 8601 format). end_time: New end time (ISO 8601 format).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adset_idYes
nameNo
statusNo
daily_budgetNo
lifetime_budgetNo
targeting_jsonNo
start_timeNo
end_timeNo
Behavior4/5

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

With no annotations, the description carries full burden. It reveals the supervised write process (validation, snapshot, rollback, verification), enforces budget constraints, and notes activation validation. It could mention authorization requirements or error handling, but overall is informative.

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 well-structured with clear sentence, procedure, notes, and arg list. While slightly lengthy due to necessary detail, it avoids redundancy and is front-loaded with the core purpose.

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 no output schema or annotations, the description covers tool behavior and parameters comprehensively but lacks mention of return value or error scenarios. It could briefly state what is returned (e.g., updated ad set details).

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 must explain all parameters. It does so thoroughly: each arg has meaning, allowed values, constraints (e.g., mutual exclusivity of budgets, targeting JSON requirements), and examples. This far exceeds schema information.

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 clearly states 'Update an existing ad set' with specific verb and resource. It differentiates from siblings like create_adset and duplicate_adset by focusing on updates, and includes detailed rules about budgets that are unique to 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?

The description provides explicit guidance on when to use budget updates (only for ABO ad sets, blocked for CBO campaigns), and explains targeting partial updates. However, it does not explicitly contrast with sibling tools like update_campaign or update_ad, though the name and context imply the scope.

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/brandu-mos/konquest-meta-ads-mcp'

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