Skip to main content
Glama

meta_ads_ad_rules_delete

Permanently delete a Meta Ads automated rule. The rule stops firing instantly and its evaluation history is purged.

Instructions

Deletes an Automated Rule. Returns a success flag. Destructive — the rule stops firing immediately and its evaluation history is purged. Not automatically reversible — record before-state with mureo_state_action_log_append if you may need to roll back (and note that re-creating the rule assigns a new rule_id, which can break downstream references). For temporary suspension prefer meta_ads_ad_rules_update with status=DISABLED.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rule_idYesRule ID to delete.
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.
Behavior5/5

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

Discloses destructive nature, immediate rule stop, history purge, non-reversibility, and downstream reference breakage. No annotations exist, so description carries full burden and does so thoroughly.

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?

Concise, multiple sentences earning their place: action, behavior, warning, alternative. Front-loaded with main purpose.

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?

Given destructive complexity and no output schema, description covers all essential points: effect, reversibility, alternative, and side effect on rule_id. Complete for agent decision-making.

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 baseline 3. Description does not add extra meaning beyond schema descriptions for account_id and rule_id. No further parameter guidance provided.

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?

Description clearly states 'Deletes an Automated Rule' with a specific verb and resource. Distinguishes from sibling meta_ads_ad_rules_update by prefenrring it for suspension, satisfying high purpose clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (delete, destructive) and when not to use (prefer update with DISABLED for temporary suspension). Provides alternative tool and action, meeting all guidelines criteria.

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