AdCopilot

Google Ads: remove account-level negative keywords

remove_account_negatives

DestructiveIdempotent

Takes account-level negative keywords back out.

The inverse of add_account_negatives: pass the same text and match
type. Every campaign in the account can show for those searches again
at once, running ones included, which can raise what they spend. Only
keywords are taken out of the account-level list; the list and its link
to the account stay, even when it is left empty. An account with no
account-level list has nothing to take out: every keyword is reported
in not_found and nothing is created or sent.

Text is matched ignoring case and extra spaces, and the match type must
match too. A keyword the list does not hold is reported in not_found
and nothing is done for it.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    keywords: List of keyword objects, each with:
        - text: The keyword text (e.g., "free").
        - match_type: One of: EXACT, PHRASE, BROAD. Default: BROAD,
          as in add_account_negatives.

Returns:
    Dictionary with the account-level list's shared_set_id (null when
    the account has none), removed (text, match_type and resource_name
    of each keyword taken out), not_found and keywords_removed.

Tools revision: d80f65c0.

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": {
      "customer_id": "<customer_id>",
      "keywords": "<keywords>"
    },
    "name": "remove_account_negatives"
  }
}

Input Schema

Name	Required	Description	Default
`keywords`	Yes
`customer_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond annotations, the description discloses important effects: campaigns can immediately show for those searches again, including running campaigns, which may raise spend. It also states that the list and its account link remain even when empty, and that missing keywords are reported in not_found without being changed. This adds substantial behavioral context for a destructive mutation.

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 front-loaded and well structured, with the destructive effect and scope stated before the parameter details. It is slightly repetitive around match-type matching and not_found handling, and the Returns section partially duplicates what the output schema can carry, but overall it is appropriately sized for a destructive tool.

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

Completeness5/5

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

Given a destructive mutation with zero schema description coverage, the description covers inputs, matching semantics, edge cases, side effects, and return fields. It is complete enough for an agent to invoke it correctly without needing to infer account-level behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates fully by documenting customer_id as numbers only without hyphens and by describing the keywords objects with text and match_type. It also specifies allowed match types EXACT, PHRASE, and BROAD plus the default BROAD, which the schema does not provide.

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 states a specific action and resource: taking account-level negative keywords out of the account-level list. It clearly distinguishes itself from add_account_negatives as the inverse operation and scopes the behavior to account-level negatives, which separates it from list-item or campaign-level removal siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains when to use it by reference to add_account_negatives and by stating that the same text and match type should be passed. It also covers edge cases such as an account with no account-level list and keywords not present in the list. It does not explicitly contrast with remove_negative_keywords or remove_from_negative_keyword_list, but the account-level scope is clear.

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

All AdCopilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?