Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

meta_ads_audiences_delete

Delete a Meta Custom Audience to clean up ad account targeting. Verify ad set usage first, then remove the audience to avoid disrupting delivery.

Instructions

Deletes a Custom Audience. Returns a success flag. Destructive — any ad sets currently targeting this audience lose the targeting source and may stop delivering. Not automatically reversible — record before-state with mureo_state_action_log_append if you may need to roll back (and note that re-creation does not restore the original approximate_count). Call meta_ads_audiences_get first to confirm which ad sets use it (search ad_sets.list targeting specs client-side), and consider pausing those ad sets first.

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.
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.
audience_idYesAudience ID to delete.

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.5/5.0
Behavior5/5

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

No annotations are provided, so the description fully carries the burden of behavioral disclosure. It explicitly states the destructive effect on ad sets, the lack of automatic reversibility, the approximate_count caveat on re-creation, and suggests a rollback path via mureo_state_action_log_append. This is exceptionally transparent for a mutation tool.

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 dense but every sentence contributes critical information: the action, the return value, the destructiveness, the irreversibility, the pre-flight checks, and the rollback suggestion. It is front-loaded with the primary purpose and impact, and there is no wasted wording.

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 three parameters, no output schema, and no annotations, the description covers all essential context: impact on ad sets, non-reversibility, re-creation caveat, pre-call verification steps, and rollback guidance. An agent has enough information to call the tool correctly and safely.

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% and each parameter (reason, account_id, audience_id) is already described in the schema. The description does not add additional parameter-specific semantics beyond what the schema provides, so it meets the baseline of 3 without exceeding it.

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 clear action and object: 'Deletes a Custom Audience.' It also mentions the return value ('Returns a success flag') and is easily distinguished from sibling tools like meta_ads_audiences_get, list, and create. The verb and resource are 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 Guidelines4/5

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

The description provides concrete guidance on when to use the tool and what to do before calling it: confirm usage via meta_ads_audiences_get, inspect ad set targeting specs, and consider pausing ad sets. It does not explicitly contrast with alternatives, but the destructive nature and precautionary steps are clearly stated, giving the agent a solid usage framework.

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