Skip to main content
Glama

meta_ads_ad_rules_update

Update an existing Meta Ads automated rule. Modify name, status, or evaluation/execution/schedule specs with partial merge or full replace. Disable to pause without losing 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.
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.
Behavior5/5

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

With no annotations, the description fully discloses mutation behavior, non-reversibility, timing of changes (next scheduled evaluation), and merge behavior for specs. No contradictions.

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 concise sentences, each providing distinct value. Front-loaded with purpose, then behavior, then usage tip. No wasted words.

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 key behavioral aspects and parameter semantics well. Lacks details on error handling, required permissions, or output format beyond 'returns the updated rule', but is sufficient for the tool's complexity.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant meaning: explains partial update, merge behavior for spec fields, the role of replace_specs, and the special meaning of status=DISABLED. This goes well beyond schema descriptions.

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 the tool updates fields on an existing Automated Rule with partial update semantics, and it returns the updated rule. This distinguishes it from siblings like create, delete, get, and 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?

Provides guidance on when to use DISABLED status instead of deleting to preserve history, and recommends recording before-state for rollback. However, it does not explicitly compare or contrast with other tools like create or delete for similar actions.

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