Meta MCP Server

Delete Campaign

meta_delete_campaign

Destructive

Delete a campaign permanently by providing its ID. This action archives the campaign and cannot be undone.

Instructions

Deletes (archives) a campaign. This cannot be undone.

Args:

campaign_id (string): Campaign ID to delete

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "meta_delete_campaign"
  }
}

Input Schema

Name	Required	Description	Default
`campaign_id`	Yes	Campaign ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.2Jun 15, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already mark the operation destructive and non-read-only, and the description adds the crucial warning 'This cannot be undone,' which is not in the structured metadata. It also reveals that deletion is actually an archival action, providing meaningful clarity about the underlying behavior. No contradiction with annotations.

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 compact and front-loads the core action and irreversibility before the argument block. The Args section is redundant with the input schema, but the overall length is appropriate for a one-parameter tool. There is no filler or irrelevant detail.

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

Completeness4/5

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

For a one-parameter destructive mutation tool, the description plus annotations and schema covers the essential facts: what is deleted, that it is archival, and that the operation is irreversible. It does not describe return values, permissions, or effects on child adsets and ads, but these are not necessary to invoke the tool correctly. The absence of an output schema is not a critical gap here.

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?

Input schema has 100% coverage and already documents campaign_id as 'Campaign ID'; the description only restates it as 'Campaign ID to delete' without adding format, source, or likely-value guidance. This meets the baseline for high schema coverage but provides no extra semantic value. The agent gains nothing beyond what the schema already provides.

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?

States a specific verb ('Deletes (archives)') and resource ('a campaign'), and the irreversibility warning clarifies the operation's meaning. This clearly distinguishes it from sibling delete tools for ads, posts, and adsets by targeting the campaign resource. No ambiguity about what the tool operates on.

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 description conveys that this is the destructive campaign-removal operation, which differentiates it from meta_get_campaign, meta_update_campaign, and other campaign tools by implication. However, it never explicitly states when to use this tool rather than an alternative or mentions prerequisites such as pausing or listing campaigns first. The usage guidance is adequate but left to inference.

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

Deploy Server