agent1st-ads-mcp

delete_meta_campaign

Permanently remove a Meta campaign and all associated ad sets and ads. This action cannot be undone, so use it to completely delete campaigns rather than temporarily pausing them.

Instructions

Permanently delete a Meta campaign and all its ad sets and ads. Cannot be undone. Use pause_meta_campaign to stop spending temporarily. Requires Starter plan or higher.

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": "delete_meta_campaign"
  }
}

Input Schema

Name	Required	Description	Default
`campaign_id`	Yes	Meta campaign ID to permanently delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Mar 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and does so effectively: it discloses the irreversible nature ('Cannot be undone'), the destructive scope (deletes campaign, ad sets, and ads), and authorization requirements (Starter plan or higher). It lacks details on rate limits or error handling, but covers key behavioral traits.

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?

Three sentences with zero waste: the first states the action and scope, the second warns about irreversibility and provides an alternative, and the third specifies prerequisites. Each sentence adds critical information, making it front-loaded and efficient.

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 destructive tool with no annotations and no output schema, the description is largely complete: it covers purpose, usage, behavioral risks, and prerequisites. It could mention response format or error cases, but given the simplicity (one parameter, no output schema), it provides sufficient context for safe use.

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 description coverage is 100%, so the schema already documents the single parameter (campaign_id). The description adds no additional parameter details beyond what the schema provides, such as format examples or constraints, meeting the baseline for high schema coverage.

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 the specific action ('permanently delete') and resource ('Meta campaign and all its ad sets and ads'), distinguishing it from siblings like pause_meta_campaign. It goes beyond the tool name by specifying the scope of deletion.

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?

It explicitly provides when to use this tool (for permanent deletion) versus an alternative (pause_meta_campaign for temporary stopping), and includes prerequisites (requires Starter plan or higher), offering comprehensive guidance.

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

Deploy Server