Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

meta_ads_campaigns_update

Update specific fields on an existing Meta Ads campaign, leaving unmentioned fields unchanged. Use it to change name, budget, or bid strategy; for status changes, prefer pause/enable tools.

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.
bid_strategyNoBid strategy for automatic auction bidding. LOWEST_COST_WITHOUT_CAP is fully automatic (do NOT set bid_amount). LOWEST_COST_WITH_BID_CAP and COST_CAP both require a bid_amount on the ad set (the cap). LOWEST_COST_WITH_MIN_ROAS requires bid_constraints.roas_average_floor on the ad set. When set on the campaign, budgets typically live at the campaign (CBO) level; when set on the ad set, at the ad-set level.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / bid_strategy
      Added value: +{
+  "description": "Bid strategy for automatic auction bidding. LOWEST_COST_WITHOUT_CAP is fully automatic (do NOT set bid_amount). LOWEST_COST_WITH_BID_CAP and COST_CAP both require a bid_amount on the ad set (the cap). LOWEST_COST_WITH_MIN_ROAS requires bid_constraints.roas_average_floor on the ad set. When set on the campaign, budgets typically live at the campaign (CBO) level; when set on the ad set, at the ad-set level.",
+  "enum": [
+    "LOWEST_COST_WITHOUT_CAP",
+    "LOWEST_COST_WITH_BID_CAP",
+    "COST_CAP",
+    "LOWEST_COST_WITH_MIN_ROAS"
+  ],
+  "type": "string"
+}
  2. Addedv0.9.12
  3. Removedv0.9.6
  4. Addedv0.9.2
  5. Removedv0.9.1
  6. Addedv1.0.5

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description discloses mutating behavior, non-reversibility, and suggests mureo_state_action_log_append for rollback. It also explains partial update and return value. Lacks permission/rate-limit details, but covers the core behavioral traits.

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?

Five short sentences, each earns its place: purpose, partial update, return value, mutation warning with rollback suggestion, and sibling alternatives. Zero redundancy and front-loaded with the primary action.

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?

Combined with the schema, the description covers purpose, mutation, rollback, alternatives, and return value. It doesn't mention error cases or permissions, but the schema thoroughly documents parameters and constraints.

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?

All 6 parameters have schema descriptions (100% coverage). The description adds only general partial-update semantics already implied by the schema, so no additional parameter-level value; baseline 3 is appropriate.

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 'Updates fields on an existing campaign', giving a specific verb and resource. It also distinguishes from sibling tools by noting partial update behavior and explicitly directing status-only transitions to meta_ads_campaigns_pause/enable.

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 when-to-use guidance (updating fields) and when-not-to-use (status-only transitions prefer pause/enable tools). It also advises recording before-state for rollback, offering clear context and alternatives.

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