AdCopilot

Google Ads: create negative keyword list

create_negative_keyword_list

Creates a shared negative keyword list, optionally with its keywords.

A negative keyword list is one blocklist that many campaigns can share:
attach it with attach_negative_keyword_list and every attached campaign
stops showing for its words. The list does nothing until it is attached.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    name: Name of the list, unique among the account's negative keyword
        lists (1-255 characters).
    keywords: Optional keywords to put in the list, each with:
        - text: The keyword text (e.g., "free").
        - match_type: One of: EXACT, PHRASE, BROAD. Default: BROAD.
        Exact duplicates are dropped. More can be added later with
        add_to_negative_keyword_list, and taken out with
        remove_from_negative_keyword_list.

Returns:
    Dictionary with the list's shared_set_id and resource name, 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>",
      "name": "<name>"
    },
    "name": "create_negative_keyword_list"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`keywords`	No
`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.5/5.0

Behavior4/5

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

Annotations already declare it is a non-destructive, non-idempotent write, so the bar is lower, yet the description adds real behavior: exact duplicates are dropped, the name must be unique among the account's negative keyword lists, and the list is inert until attached. It does not mention permission requirements or what happens on duplicate name collisions, which keeps it short of a 5.

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?

Front-loaded purpose sentence followed by a short conceptual explanation, then consistently formatted Args and Returns blocks. Slightly verbose for a three-parameter tool, but every line carries operational meaning.

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?

An output schema exists, so the Returns section is a bonus rather than a necessity. Combined with full parameter documentation, dedup behavior, and the attach dependency, an agent has everything needed to call this correctly on the first attempt.

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 coverage is 0%, so the description must carry all parameter meaning, and it does: customer_id format (numbers only, no hyphens), name length and uniqueness constraint, and the keywords item shape with text and match_type enum EXACT/PHRASE/BROAD plus BROAD default. This is strictly more information than the schema title fields 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?

States a specific verb and resource ('Creates a shared negative keyword list, optionally with its keywords') and immediately frames the object's role as a shared blocklist, which distinguishes it from add_negative_keywords and add_account_negatives. The reader knows exactly what artifact this call produces.

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?

Explicitly says the list does nothing until attached via attach_negative_keyword_list, and routes later edits to add_to_negative_keyword_list and remove_from_negative_keyword_list. It doesn't contrast with account-level negatives (add_account_negatives / add_negative_keywords), which is the one remaining ambiguity among siblings.

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?