Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_ad_rules_delete

Delete a Meta Ads automated rule to stop it immediately and purge its history. This action is irreversible; use only when no rollback is needed.

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
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.9.12
  4. Removedv0.9.6
  5. Addedv0.9.2
  6. Removedv0.9.1
  7. Addedv1.0.5

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses that the operation is destructive, stops firing immediately, purges evaluation history, is not automatically reversible, and that re-creating the rule assigns a new rule_id which can break downstream references.

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?

Every sentence adds value: core action, return result, destructive consequences, rollback guidance, and the alternative for temporary suspension. Information is front-loaded starting with the main verb and resource, with no filler or tautology.

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 destructive tool with no output schema and no annotations, the description covers the essential context: what happens, what is returned, why to avoid it unless permanent, how to preserve rollback state, and which sibling to prefer for non-destructive needs. Nothing critical is missing.

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 description coverage is 100%, so the baseline is 3. The description does not add parameter-level details beyond the schema, but it does add relevant behavioral context about rule_id (new ID on recreation) which indirectly reinforces the importance of that parameter.

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 opens with a specific verb and resource: 'Deletes an Automated Rule.' It clearly distinguishes this tool from the sibling meta_ads_ad_rules_update by framing deletion as final, and the return behavior is stated ('Returns a success flag').

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?

Provides explicit guidance on when NOT to use it: 'For temporary suspension prefer meta_ads_ad_rules_update with status=DISABLED.' It also names a rollback alternative, mureo_state_action_log_append, making the choice between tools and supporting actions clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools