Skip to main content
Glama

meta_ads_ad_rules_create

Create automated rules in Meta Ads to schedule evaluations and trigger actions like pausing ads, changing budgets, or sending notifications when performance conditions are met.

Instructions

Creates a new Automated Rule that Meta evaluates on the configured schedule and fires actions when the trigger matches. Returns the new rule_id. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. Common patterns: CPA-spike alert (execution NOTIFICATION), auto-pause ads with low ROAS (execution PAUSE), scale winners (execution CHANGE_BUDGET). evaluation_spec and execution_spec are Meta's JSON schemas — see Meta Ads Automated Rules API docs for the field set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRule name shown in Ads Manager. Should name the trigger and action (e.g. 'Pause ads CPA > target × 2').
statusNoInitial status. Default ENABLED. Create with DISABLED and enable later to stage the rule without side effects.
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.
schedule_specNoWhen the rule runs. Shape: {schedule_type: SEMI_HOURLY | DAILY | CUSTOM, schedule: [time specs]}. Default SEMI_HOURLY evaluates every 30 minutes.
execution_specYesAction definition. Shape: {execution_type: NOTIFICATION | PAUSE_CAMPAIGNS | UNPAUSE_CAMPAIGNS | CHANGE_BUDGET | CHANGE_BID, execution_options: [...]}. Budget/bid changes use delta or absolute value per execution_options.
evaluation_specYesTrigger definition. Shape: {evaluation_type: SCHEDULE | TRIGGER, filters: [{field, operator, value}, ...]}. Filters combine with AND; for OR create multiple rules.
Behavior4/5

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

With no annotations, description carries full burden. It discloses mutation, irreversibility, and recommends logging before-state. Also mentions return value (rule_id). No contradictions. Some details like rate limits or auth requirements missing, but acceptable.

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, tightly packed: purpose, mutation warning, patterns, schema reference. No wasted words, front-loaded with essential info.

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?

Given nested JSON schemas and no output schema, description covers key aspects: creation, scheduling, actions, and rollback. Could mention what happens on failure or how to interpret the rule_id, but overall sufficient for a complex tool.

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 describes all 6 parameters. Description adds value by illustrating evaluation_spec and execution_spec as Meta JSON schemas, providing shape hints, and noting schedule_spec default. Also references external docs for further details.

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?

Clearly states it creates an Automated Rule, specifying the schedule and trigger-action behavior. Returns rule_id. Common patterns further clarify intended use. Distinguished from sibling tools (delete, get, list, update) by being a create operation.

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?

Lists common patterns (CPA-spike alert, auto-pause, scale winners) and advises recording before-state for rollback. Though it doesn't explicitly state when not to use, it provides sufficient context for typical scenarios.

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