AdCopilot

Google Ads: add account-level negative keywords

add_account_negatives

Adds account-level negative keywords: words blocked in every campaign.

Use for words the business never wants to show for anywhere (e.g.
brand-safety terms, "free", "jobs"). In the Google Ads API these live in
the account's single account-level negative keyword list (a shared set
of type ACCOUNT_LEVEL_NEGATIVE_KEYWORDS, linked to the account by a
CustomerNegativeCriterion). This tool adds the words to that list if the
account already has one, and otherwise creates the list, adds the words
and links it to the account. remove_account_negatives takes words back
out.

Limits (Google's): an account has at most one account-level list, of up
to 1,000 keywords. Google applies it to the search and shopping
inventory of Search, Shopping, Performance Max, App, Smart and Local
campaigns — not to Display or Video placements.

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.
        Exact duplicates are dropped.

Returns:
    Dictionary with the account-level list's shared_set_id, whether it
    was created now, and the keywords added.

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": "add_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.8/5.0

Behavior5/5

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

Beyond the annotations, the description explains the Google Ads shared-set mechanics, that it creates and links the list if absent, the 1,000-keyword account limit, duplicate dropping, and which campaign types the negatives affect versus Display and Video.

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?

The description is front-loaded with the core purpose, then structured into usage, API behavior, limits, Args, and Returns. Every section adds useful information without redundant wording.

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?

For a two-parameter mutation tool with complex Google Ads semantics, the description covers purpose, prerequisites, creation-if-missing behavior, limits, applicability, parameter details, and return summary. An agent has everything needed to invoke it correctly.

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% and the schema itself does not define keyword object fields, but the description fully documents customer_id formatting and each keyword's text, match_type options, default, and duplicate handling. This compensates completely for the schema gap.

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 verb and resource: adding account-level negative keywords, explicitly defined as words blocked in every campaign. This scope distinguishes it from campaign-level or list-management siblings without requiring schema inspection.

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 gives a clear when-to-use case with examples (brand-safety terms, "free", "jobs") and points to remove_account_negatives for reversal. It does not explicitly distinguish when to use this versus add_negative_keywords or add_to_negative_keyword_list, but the account-level scope is strongly implied.

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?