> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete Campaign

> Use the delete_campaign MCP tool on the DialNexa remote MCP server.

<span data-api-safety-label="destructive"><Badge color="red" size="sm" shape="pill">Destructive</Badge></span>

Deletes a campaign from the organization's list — the same delete the dashboard offers on a draft campaign. Removes the campaign only; calls it already placed keep their own records. Allowed for campaigns that are not live: draft, completed, or cancelled. A campaign that is still going (running, paused, scheduled, waiting) CANNOT be deleted — cancel it first with update\_batch\_call\_status, then delete. Requires confirm: true, and this cannot be undone.

## Parameters

| Name       | Type      | Required | Description                                                                                         |
| ---------- | --------- | -------- | --------------------------------------------------------------------------------------------------- |
| `batch_id` | `string`  | Yes      | The campaign ID, e.g. batch\_abc123                                                                 |
| `confirm`  | `boolean` | Yes      | Must be true. Set this only after the user has explicitly approved deleting this specific campaign. |

## Before you call

* Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
* Provide the required parameters: `batch_id`, `confirm`.
* Set `confirm: true` only after the user approves the exact target and action.

## Example MCP request

Send `tools/call` after your client completes MCP initialization. Replace placeholder values with IDs and inputs from your workspace. For object and array parameters, follow the nested requirements in the parameter description instead of treating an empty value as complete.

```json theme={null}
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_campaign",
    "arguments": {
      "batch_id": "batch_abc123",
      "confirm": true
    }
  }
}
```

The server returns one text content block. Parse `content[0].text` as JSON when the tool succeeds. See [MCP responses and errors](/docs/mcp-tools/errors) for the full envelope and failure behavior.

## Verify the result

Confirm the response is not marked `isError`. Call [List Campaigns](/docs/mcp-tools/batch-calls/list-campaigns) to read the affected resource. Verify that the target is removed or disconnected before reporting completion.

## Retry safety

This tool can remove or disconnect a resource. Confirm the exact target first, and do not retry after an uncertain result until you verify the current state.

## Related MCP tools

* [Update Batch Call Status](/docs/mcp-tools/batch-calls/update-batch-call-status): `update_batch_call_status`
* [List Campaigns](/docs/mcp-tools/batch-calls/list-campaigns): `list_campaigns`
* [Get Campaign](/docs/mcp-tools/batch-calls/get-campaign): `get_campaign`

## Related guides

* [Connect to the DialNexa MCP server](/docs/mcp-tools/overview)
* [Batch Calls MCP tools](/docs/mcp-tools/batch-calls/overview)
* [MCP responses and errors](/docs/mcp-tools/errors)