Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by AbnerZx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

audiences_delete_saved

Permanently delete a saved audience from Meta Ads. Confirmation required to prevent accidental removal.

Instructions

Permanently delete a saved audience.

KNOWN LIMITATION: also gated by the saved_audiences write capability.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "saved_audience_id": "<saved_audience_id>"
    },
    "name": "audiences_delete_saved"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
saved_audience_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses permanence (irreversible) and a gating limitation, but it fails to disclose the role of the `confirm` parameter, which is critical for a destructive operation. This is a notable gap.

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 two sentences, front-loaded with the core action, and the limitation note adds valuable context without padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description should indicate expected results or side effects, but it does not. It also omits the confirm behavior, making it incomplete for a destructive tool with 2 parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain either parameter. While 'saved_audience_id' is implicitly the target, the `confirm` boolean is entirely unexplained, leaving the agent uncertain about whether it must be set to true.

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 uses a specific verb ('delete') with a clear resource ('saved audience') and qualifies it as 'permanently', distinguishing it from sibling tools like audiences_update_saved and audiences_list_saved.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the verb and resource—use this tool to permanently remove a saved audience. However, there is no explicit guidance about alternatives or when not to use it, nor any mention of prerequisite conditions beyond the note about the write capability.

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