Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_ad_rules_update

Update fields on an existing Meta Ads automated rule; only supplied fields change, and the updated rule is returned.

Instructions

Updates fields on an existing Automated Rule. Partial update — only supplied fields are changed. Returns the updated rule. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. Changes take effect on the next scheduled evaluation. To temporarily suspend a rule, set status=DISABLED rather than deleting it so history is preserved.

Input Schema

NameRequiredDescriptionDefault
nameNoNew rule name.
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
statusNoNew status. DISABLED pauses evaluation without deleting history.
rule_idYesRule ID to update.
approvalNoExternal approval this change carries out (recorded and shown, never verified)
expectedNoExpected effects [{metric, direction, target?, horizon_days?, primary?}], exactly one primary:true when several; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold.
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.
decision_idNoA proposed decision this change carries out.
replace_specsNoWhen true, supplied spec objects replace the whole spec instead of merging onto the current one. Default false (safe merge).
schedule_specNoSchedule changes. Merged onto the current spec by default; set replace_specs=true to replace it.
execution_specNoAction changes. Merged onto the current spec by default; array values are replaced wholesale. Set replace_specs=true to replace it.
evaluation_specNoTrigger changes. Merged onto the current spec by default (top-level keys you omit are kept), so you can change one facet without dropping the rest. Note: array values such as `filters` are replaced wholesale — include every condition you want to keep. Set replace_specs=true to replace the whole spec.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.33.0
    • changedInput schema / properties / expected / description
      Previous value: -"Expected effects [{metric, direction, target?, horizon_days?}]; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold."New value: +"Expected effects [{metric, direction, target?, horizon_days?, primary?}], exactly one primary:true when several; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold."
  2. Changed1 schema field changedv0.28.0
    • addedInput schema / properties / approval
      Added value: +{
+  "additionalProperties": false,
+  "description": "External approval this change carries out (recorded and shown, never verified)",
+  "properties": {
+    "approved_at": {
+      "maxLength": 64,
+      "type": "string"
+    },
+    "approved_by": {
+      "maxLength": 80,
+      "type": "string"
+    },
+    "reference": {
+      "maxLength": 128,
+      "type": "string"
+    }
+  },
+  "required": [
+    "reference",
+    "approved_by",
+    "approved_at"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changedv0.26.0
    • addedInput schema / properties / decision_id
      Added value: +{
+  "description": "A proposed decision this change carries out.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / expected
      Added value: +{
+  "description": "Expected effects [{metric, direction, target?, horizon_days?}]; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold.",
+  "maxItems": 12,
+  "type": "array"
+}
  4. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  5. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  6. Changed4 schema fields changedv0.10.7
    • changedInput schema / properties / evaluation_spec / description
      Previous value: -"New trigger definition. Replaces the entire spec — fetch current via meta_ads_ad_rules_get first if merging."New value: +"Trigger changes. Merged onto the current spec by default (top-level keys you omit are kept), so you can change one facet without dropping the rest. Note: array values such as `filters` are replaced wholesale — include every condition you want to keep. Set replace_specs=true to replace the whole spec."
    • changedInput schema / properties / execution_spec / description
      Previous value: -"New action definition. Replaces the entire spec."New value: +"Action changes. Merged onto the current spec by default; array values are replaced wholesale. Set replace_specs=true to replace it."
    • addedInput schema / properties / replace_specs
      Added value: +{
+  "description": "When true, supplied spec objects replace the whole spec instead of merging onto the current one. Default false (safe merge).",
+  "type": "boolean"
+}
    • changedInput schema / properties / schedule_spec / description
      Previous value: -"New schedule definition."New value: +"Schedule changes. Merged onto the current spec by default; set replace_specs=true to replace it."
  7. Addedv0.9.12
  8. Removedv0.9.6
  9. Addedv0.9.2
  10. Removedv0.9.1
  11. Addedv1.0.5

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it declares the tool mutating, not automatically reversible, names the logging tool for before-state, and explains that changes only take effect on the next scheduled evaluation. Merge-vs-replace behavior and rollback path are both disclosed.

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, front-loaded with what the tool does, then irreversibility, then timing, then the suspend-vs-delete tip. No filler; each sentence carries a distinct operational fact.

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?

For a 12-parameter mutation tool with no annotations and no output schema, the description supplies the missing behavioral context: reversibility, effect timing, rollback procedure, and return value ("Returns the updated rule"). Nothing an agent needs before calling is absent.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds value by stating "partial update — only supplied fields are changed" and by linking status=DISABLED to the delete alternative, which clarifies two params beyond their schema text. The remaining params are left to the schema.

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?

States a specific verb and resource ("Updates fields on an existing Automated Rule") plus scope (partial update, returns the updated rule). The word "existing" implicitly separates it from meta_ads_ad_rules_create and the mutation framing separates it from meta_ads_ad_rules_get/list.

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?

Gives real operational guidance: set status=DISABLED rather than deleting to preserve history, and record before-state with mureo_state_action_log_append if rollback may be needed. It does not explicitly contrast with sibling update tools or state prerequisites, so it falls just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools