Skip to main content
Glama

meta_ads_audiences_delete

Delete a Custom Audience from Meta Ads. First, find which ad sets use it to prevent delivery disruption.

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. Reversible via rollback_apply within Meta's standard retention window, but 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
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.
Behavior5/5

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

No annotations exist, so the description carries full burden. It thoroughly discloses destructiveness, impact on ad sets (loss of targeting, potential delivery stop), limited reversibility, and data loss regarding approximate_count. Complete transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph that packs essential information without excessive verbosity. Well-structured, though slightly longer than needed for a two-parameter tool.

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 the simple structure (2 params, no output schema, no nested objects), the description is remarkably complete. It covers prerequisites, side effects, rollback details, and post-deletion behavior, leaving no critical gaps.

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 is 3. The description adds minimal extra meaning beyond what's in the schema (e.g., account_id optionality noted). No additional semantic value for the parameters.

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 a Custom Audience and returns a success flag. It distinguishes itself from siblings by emphasizing the destructive nature and side effects, making its purpose unmistakable.

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: call meta_ads_audiences_get first to identify affected ad sets, consider pausing them, and notes reversibility via rollback_apply. This helps the agent decide when and how to use the tool appropriately.

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