Skip to main content
Glama

meta_ads_ad_rules_create

Create automated rules for Meta Ads that evaluate on a schedule and fire actions like notifications, pausing campaigns, or adjusting budgets when performance triggers match.

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, reversible via rollback_apply (rollback disables the rule; actions the rule already took stand). 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
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.
nameYesRule name shown in Ads Manager. Should name the trigger and action (e.g. 'Pause ads CPA > target × 2').
evaluation_specYesTrigger definition. Shape: {evaluation_type: SCHEDULE | TRIGGER, filters: [{field, operator, value}, ...]}. Filters combine with AND; for OR create multiple rules.
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.
schedule_specNoWhen the rule runs. Shape: {schedule_type: SEMI_HOURLY | DAILY | CUSTOM, schedule: [time specs]}. Default SEMI_HOURLY evaluates every 30 minutes.
statusNoInitial status. Default ENABLED. Create with DISABLED and enable later to stage the rule without side effects.
Behavior4/5

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

Discloses mutation and reversibility via rollback_apply, noting that actions already taken persist. No annotations exist, so the description carries the burden; it covers key behavioral traits but omits auth requirements or rate limits.

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?

Front-loaded with purpose, followed by behavioral note, patterns, and schema reference. Every sentence contributes meaningfully; no fluff. Well-structured.

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 return value (rule_id), default schedule, and nested object shapes. References Meta docs for full field set. Missing error scenarios or rate limits, but given complexity, it is fairly complete.

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?

Schema coverage is 100%, so the baseline is 3. The description adds common patterns and clarifies evaluation_spec/execution_spec shapes, but these details are already in the schema descriptions. Overall, marginal added value beyond 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?

The description clearly states 'Creates a new Automated Rule' with specific verb and resource. It distinguishes from sibling tools (meta_ads_ad_rules_delete, get, list, update) by focusing on creation.

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 common patterns (CPA-spike alert, auto-pause ads, scale winners) and references Meta docs for JSON schemas. However, lacks explicit when-not-to-use guidance or alternatives for manual creation.

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