Skip to main content
Glama

meta_ads_ad_rules_delete

Permanently delete an Automated Rule – stops firing immediately and purges its evaluation history. Not reversible via update; for temporary suspension, use update with DISABLED status.

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?

With no annotations, the description fully discloses destructive behavior: rule stops firing immediately, evaluation history purged, and irreversible in terms of rule_id consistency. It also notes the rollback option with its caveat. This exceeds the required level of transparency.

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?

The description is concise (2 sentences plus a clarifying sentence), front-loaded with the primary action and return value. Every sentence provides essential information without redundancy.

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?

For a delete tool with 2 parameters and no output schema, the description covers the return value (success flag), side effects, reversibility, and alternative. It is fully complete for the agent to make an informed decision.

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?

Both parameters (account_id, rule_id) are fully described in the schema (100% coverage). The description adds no additional meaning beyond the schema, so a baseline of 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 the action ('Deletes an Automated Rule') and the outcome ('Returns a success flag'). It distinguishes from siblings like meta_ads_ad_rules_update (which can disable) and rollback_apply (which re-creates with a new rule_id).

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 tells when to use (permanent deletion) and when not to (temporary suspension should use meta_ads_ad_rules_update with status=DISABLED). Also mentions consequences and the alternative rollback_apply, providing clear guidance for agent selection.

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