Skip to main content
Glama

meta_ads_campaigns_update

Modify specific fields of an existing Meta Ads campaign, such as name, status, or daily budget, without affecting other settings. Partial update returns the updated campaign and supports rollback for reversibility.

Instructions

Updates fields on an existing campaign. Partial update — only the supplied fields are changed. Returns the updated campaign. Mutating, reversible via rollback_apply. For status-only transitions prefer meta_ads_campaigns_pause / meta_ads_campaigns_enable, which are safer and map to a single explicit operator intent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
campaign_idYesCampaign ID to update.
nameNoNew campaign name.
statusNoNew campaign status. Prefer the dedicated meta_ads_campaigns_pause / enable tools for ACTIVE ↔ PAUSED transitions.
daily_budgetNoNew daily budget in account currency minor units (cents for USD, yen for JPY). Only settable when the campaign is configured for CBO; ad-set-level budgets must be edited via meta_ads_ad_sets_update.
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses mutability and reversibility via rollback_apply, but lacks details on authorization requirements, error states, or that the campaign must exist.

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

Conciseness5/5

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

Three concise sentences, front-loaded with purpose, succinctly covering partial update, return value, mutability, and sibling alternatives without waste.

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 5 parameters and no output schema, the description adequately covers key aspects: partial update, return value, reversibility, and distinction from simpler tools. Lacks error handling or permission details but sufficient for a typical update.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds no extra parameter-level information beyond reinforcing partial update behavior.

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?

Clearly states it updates an existing campaign with partial update semantics. Explicitly distinguishes from status-only siblings by recommending meta_ads_campaigns_pause/enable for simpler transitions.

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?

Provides explicit guidance to prefer dedicated pause/enable tools for status-only changes, making the decision boundary clear for the agent.

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