Skip to main content
Glama

meta_ads_campaigns_update

Update specific campaign fields such as name, status, or daily budget. Only provided fields are changed; returns the updated campaign.

Instructions

Updates fields on an existing campaign. Partial update — only the supplied fields are changed. Returns the updated campaign. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. 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
nameNoNew campaign name.
statusNoNew campaign status. Prefer the dedicated meta_ads_campaigns_pause / enable tools for ACTIVE ↔ PAUSED transitions.
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.
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.
Behavior4/5

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

States it is mutating, not automatically reversible, and recommends a rollback safety measure. With no annotations, the description carries the burden; it covers key behavioral traits (partial update, returns updated campaign) but lacks details like permission requirements or error behavior.

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?

Four sentences front-loaded with purpose. Every sentence adds value: purpose, partial update, return, mutability/rollback, and sibling tool guidance. No filler.

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?

Covers purpose, mutability, rollback, and comparisons. Lacks description of return value structure (though schema and output schema absent), but states 'Returns the updated campaign'. With 5 params and no annotations, it provides sufficient context for safe invocation.

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 coverage is 100%, so baseline is 3. The description adds no extra parameter-specific meaning beyond what the schema already provides (e.g., it mentions 'Partial update' generally but not per-parameter).

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?

Describes clearly that it updates an existing campaign with partial update semantics. Contrasts with sibling pause/enable tools. Sentence 'Updates fields on an existing campaign' provides specific verb and resource, and 'Partial update' adds precision.

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?

Explicitly advises to prefer meta_ads_campaigns_pause / enable for status-only transitions, and suggests recording before-state for rollback. This tells the agent when not to use this tool and what alternatives exist.

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