---
title: "Remove campaign negative keywords (permanent)"
method: POST
path: "/api/v1/tools/google_remove_negative_keywords/execute"
tags: ["Google Ads"]
---

# Remove campaign negative keywords (permanent)

`POST /api/v1/tools/google_remove_negative_keywords/execute`

## Request

- Base URL: `https://adako.ai`
- URL: `https://adako.ai/api/v1/tools/google_remove_negative_keywords/execute`
- Auth: HTTP bearer

Deletes negative keywords from a campaign so those queries can trigger ads again. This is the only tool in Adako that removes anything, and the removal is permanent: a removed criterion cannot be restored, only re-added as a new one.
Use when: the user has confirmed that a specific negative is blocking traffic they want, and you have shown them the exact list by name.
Do not use when: the user asked to "turn off", "stop" or "pause" something — that is never a removal. Negatives cannot be paused; if the user is unsure, leave them in place.
Requires confirm_delete: true. Ask the user first, in plain words, naming every negative that will be deleted. Ids that are not negatives on this campaign are reported back rather than silently ignored.
Removing a negative widens matching immediately, which can increase spend.
If you are unsure which account, campaign or period the user means, ask them — do not guess ids or dates.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `arguments` object, required
    - `customer_id` string: Google Ads customer id (10 digits, dashes optional). Omit to use the primary account; list_connected_accounts shows the valid ids.
    - `campaign_id` string, required: Campaign id as returned by google_list_campaigns.
    - `keyword_ids` string[], required: Criterion ids of the campaign negatives to remove, from google_get_campaign_targeting.
    - `confirm_delete` boolean: Must be true to remove anything. Ask the user first.
    - `idempotency_key` string: Optional caller-supplied key; identical keys never execute twice.

## Response `200`

The tool ran. A write returns proposal_id and approve_url while the change waits for approval.

- SuccessEnvelope
  - `success` unknown, required
  - `tool` string, required
  - `data` object, required: Machine-readable result.
  - `markdown` string, required: The same result written for a person or a model.
  - `quota` Quota: Task usage for the current billing period.
    - `plan` string
    - `used` integer
    - `limit` integer
    - `period_end` string
    - `upgrade_url` string
  - `proposal_id` string: Present for writes. Nothing changes on the ad platform until it is approved.
  - `approve_url` string: Where a person approves the proposal.
  - `request_id` string, required

## Other responses

- `400`: Invalid arguments, or the ad account could not be resolved.
- `401`: Missing, invalid, revoked or expired API key.
- `402`: Monthly task quota used up, or the plan does not include this tool.
- `403`: The connected ad account lacks the access level this tool needs.
- `404`: Unknown tool name.
- `409`: Not connected, reconnect needed, confirmation required, a proposal already pending or no longer pending, an identical create that failed earlier today (proposal_failed_before), a create that duplicates an approved one (duplicate_create), the ad-account limit of the plan reached (account_limit), or an Idempotency-Key reused with different arguments.
- `429`: Rate limited by Adako or by the ad platform. See Retry-After.
- `500`: Unexpected error inside Adako.
- `502`: The ad platform returned an error.

---

[API](https://skmtc.dev/adako/apis/adako-rest-api.md) · [All operations](https://skmtc.dev/adako/apis/adako-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/adako/apis/adako-rest-api/revisions/59ee60d48a56?raw)