Skip to main content
Glama
Meta Ads MCP

Meta Ads MCP

by kremnyi

delete

Destructive

Remove a Meta campaign, ad set, ad, or creative only after explicit confirmation of the exact change.

Instructions

Delete a campaign, ad set, ad, or creative. Requires explicit confirmation of this exact deletion.

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": {
      "id": "<id>",
      "change_summary": "<change_summary>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Meta object ID.
change_summaryYesConcise exact change the user approved in the current request, with budget and status.
user_confirmedYesMust be true only after explicit action-time user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds a valuable workflow constraint not in the annotations: an action-time, exact-match user confirmation is mandatory before deletion proceeds.

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?

Two short sentences, front-loaded with the affected resource types, followed by the hard requirement. No filler or redundant restatement of the tool name.

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

Completeness3/5

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

Adequate for a destructive tool: purpose and the confirmation gate are covered, and annotations carry the safety hints. It does not mention irreversibility or cascade effects (for example, deleting a campaign removing its child ad sets and ads), which matters for a destructive operation.

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 the schema already documents id, change_summary, and user_confirmed. The phrase 'this exact deletion' lightly reinforces that change_summary must match the approved object, but adds no format or syntax detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (delete) and enumerates the exact resource types affected: campaign, ad set, ad, or creative. This clearly separates it from siblings like set_status or update, though it does not name those siblings explicitly.

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?

Gives a prerequisite (explicit confirmation of this exact deletion) but no guidance on when deletion is preferred over alternatives such as set_status for pausing. Usage context is implied rather than stated.

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