Skip to main content
Glama

meta_ads_ad_sets_update

Update one or more settings on an existing Meta Ads ad set. Partial update that only changes provided fields and merges targeting changes by default.

Instructions

Updates one or more settings on an existing ad set. Partial update — only provided fields are changed. Returns the updated ad set. Mutating; not automatically reversible — record before-state if you need to roll back. For status-only transitions prefer meta_ads_ad_sets_pause / meta_ads_ad_sets_enable. Changing targeting is a safe read-modify-write by default: the supplied top-level keys are merged onto the current spec, so keys you omit are preserved. Set replace_targeting to true to replace the whole spec instead (e.g. to clear a facet).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNew ad set name.
statusNoNew ad set status. Prefer the dedicated pause/enable tools for simple ACTIVE ↔ PAUSED.
end_timeNoNew schedule end. Accepts an ISO 8601 datetime string (e.g. '2026-08-01T00:00:00+0900') or a UTC UNIX timestamp integer. Pass 0 to clear the end date so the ad set runs continuously (Meta API convention; only valid with a daily budget — a lifetime budget requires an end date).
ad_set_idYesAd set ID to update.
targetingNoTargeting spec changes. Merged onto the current spec by default (top-level keys you omit are kept). Supply only the facets you want to change, e.g. {"age_min": 25}. Set replace_targeting=true to replace the whole spec instead.
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
daily_budgetNoNew daily budget in account currency minor units. Only valid when the campaign is not using CBO. Mutually exclusive with lifetime_budget.
lifetime_budgetNoNew lifetime budget in account currency minor units (cents for USD, yen for JPY). Mutually exclusive with daily_budget. Requires the ad set to have an end_time — supply one in the same call if it is not already set.
replace_targetingNoWhen true, `targeting` replaces the entire spec instead of merging onto the current one. Use only to deliberately clear targeting facets. Default false (safe merge).
Behavior5/5

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

With no annotations, the description carries full burden. It explicitly states the operation is mutating and not automatically reversible, advising to record before-state for rollback. Also details the safe read-modify-write for targeting and the replace option.

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 concise and front-loaded with the main purpose. Every sentence adds value, though slightly more structured formatting (e.g., bullet points) could improve readability.

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 no output schema, the description mentions it returns the updated ad set. It covers all key aspects: partial update, irreversibility, targeting behavior, budget constraints, and status alternatives. Complete for an update 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?

Schema coverage is 100%, but the description adds significant value beyond schema by explaining merge semantics for targeting, end_time=0 meaning, mutual exclusivity of budgets, and replace_targeting usage.

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 the verb 'Updates', the resource 'ad set', and specifies it's a partial update. It distinguishes from siblings like meta_ads_ad_sets_pause/enable by noting they are preferred for status-only transitions.

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?

Explicitly suggests using dedicated pause/enable tools for status-only changes and explains targeting merge behavior. Could be more explicit about when not to use, but provides clear context.

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/logly/mureo'

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