Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_ad_rules_update

Partially update an existing Meta Ads automated rule by changing only supplied fields such as name, status, schedule, or trigger conditions. Set status to DISABLED to pause evaluation without deleting history.

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

TableJSON 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.
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.
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.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"
+}
  2. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. 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."
  4. Addedv0.9.12
  5. Removedv0.9.6
  6. Addedv0.9.2
  7. Removedv0.9.1
  8. 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 present, the description takes on the full disclosure burden and does so thoroughly. It calls out mutating behavior, non-reversibility, a rollback strategy, the timing of when changes take effect, and that the updated rule is returned.

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?

The description is dense but not bloated; every sentence carries distinct information. The core purpose is front-loaded, followed by update semantics, mutation risk, timing, and a practical status guidance.

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 complex 9-parameter mutation tool with nested objects and no output schema, the description covers the essential behavioral context: what changes, what does not change, side effects, reversibility, rollback, and timing. It complements the detailed schema without omitting anything an agent needs to call it safely.

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% and the schema already documents merge/replace behavior for the spec objects. The description adds useful cross-cutting semantics: partial update, safe merge default, and the fact that changes apply on the next scheduled evaluation.

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 opens with a specific verb-resource pair: 'Updates fields on an existing Automated Rule.' It immediately distinguishes this from creating, deleting, listing, or getting rules, and the 'Partial update' clarification sharpens the scope.

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?

The description gives concrete usage guidance by explaining that 'only supplied fields are changed' and explicitly recommends 'set status=DISABLED rather than deleting it' for temporary suspension. It does not explicitly name the create alternative for new rules, but the 'existing rule' wording makes the boundary clear.

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