Skip to main content
Glama

meta_ads_ad_rules_delete

Permanently deletes an Automated Rule. The rule stops firing immediately and evaluation history is purged. Use with caution; disable instead for temporary suspension.

Instructions

Deletes an Automated Rule. Returns a success flag. Destructive — the rule stops firing immediately and its evaluation history is purged. Reversible via rollback_apply (re-creates the rule), but the rule_id changes on re-create which can break downstream references. For temporary suspension prefer meta_ads_ad_rules_update with status=DISABLED.

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

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

No annotations provided, so description carries full burden. It states the rule stops firing immediately, history is purged, and re-creating changes rule_id breaking downstream references. This fully discloses destructive behavior and side effects.

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?

Three sentences, each earning its place: purpose, side effects, alternative. Front-loaded and no fluff. Highly efficient.

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?

Comprehensive for a deletion tool: covers return value, destructive behavior, reversibility, and alternative. No output schema but mentions success flag. Complete enough for an agent to use correctly.

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% with clear descriptions for both parameters. The description does not add additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 it deletes an Automated Rule and returns a success flag. It distinguishes from update (for suspension) and mentions rollback. This is specific and unambiguous.

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 provides when to use this tool vs alternatives: 'For temporary suspension prefer meta_ads_ad_rules_update with status=DISABLED.' Also mentions reversibility via rollback_apply but notes rule_id changes, which is crucial guidance.

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