Skip to main content
Glama
Sign In
Meta Ads MCP

Meta Ads MCP

by AbnerZx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ads_delete_adset

Delete an ad set and automatically remove all ads under it. Use this action to clean up campaign structures in Meta Ads.

Instructions

Delete an ad set. Cascades to all ads under it.

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": {
      "adset_id": "<adset_id>"
    },
    "name": "ads_delete_adset"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
adset_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?

It discloses cascading, which is a critical side effect. However, it omits the confirm parameter's role, reversibility, and other potential side effects, leaving gaps given no annotations are provided.

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 short sentences, direct and front-loaded, with no redundant information. Every word earns its place.

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?

For a destructive mutation tool with a confirmation flag, the description fails to explain the confirm behavior, what happens if confirm is false, or what the return value is. This is incomplete for safe and correct use.

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%, so the description must explain parameters. It implies adset_id but does not mention confirm at all, leaving the agent uncertain about its purpose and whether it affects deletion.

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 'Delete an ad set' with a specific verb and resource, and adds 'Cascades to all ads under it' which distinguishes it from related tools like delete_campaign or pause_adset.

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?

The cascade warning implies a consequence, but there is no explicit guidance on when to use this versus alternatives like pausing or editing. It also doesn't mention when not to use it.

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