AdCopilot

Google Ads: attach negative keyword list

attach_negative_keyword_list

Attaches a shared negative keyword list to a campaign.

The campaign stops showing for every word in the list, including words
added to the list later.

There is no matching detach tool: in the Google Ads API a campaign's
link to a list (CampaignSharedSet) has no settable status, so it cannot
be paused, and undoing it means removing the link. This connector does
not remove links; the user can detach a list in Google Ads under Tools >
Shared library > Exclusion lists. Single words can be taken out of the
list with remove_from_negative_keyword_list, which changes every
campaign the list is attached to.

Args:
    customer_id: The Google Ads customer ID (numbers only, no hyphens).
    campaign_id: The ID of the campaign.
    shared_set_id: The ID of the negative keyword list (from
        create_negative_keyword_list, or shared_set.id via search).

Returns:
    Dictionary with the created campaign shared set resource name.

Tools revision: 5c9bea8f.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`campaign_id`	Yes
`customer_id`	Yes
`shared_set_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The annotations already declare readOnly=false, destructive=false, and idempotent=false, but the description adds substantial context beyond them: the attachment applies to future list additions, links cannot be paused, the connector cannot remove links, and word-level removals affect every attached campaign. No annotation contradiction is present.

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 action, then adds behavioral and detach limitations before documenting Args and Returns. The extra explanation is directly relevant to correct use, and there is no redundant filler.

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 three-parameter mutation tool with an output schema, the description covers the key calling constraints, side effects, and detach/removal limitations. It leaves no important ambiguity about what the tool does or how it differs from nearby tools.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, and it does explain all three parameters. customer_id includes the useful numbers-only/no-hyphens constraint, campaign_id is identified as the campaign ID, and shared_set_id includes its provenance; however, campaign_id and shared_set_id formats are only minimally described.

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 gives a specific verb and resource: it attaches a shared negative keyword list to a campaign. It also clarifies the practical scope: the campaign stops showing for every word in the list, including words added later. This distinguishes it from siblings such as create_negative_keyword_list and remove_from_negative_keyword_list.

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

Usage Guidelines5/5

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

It clearly states when this tool is used and names alternatives: there is no detach tool, removal happens outside the connector, and individual words can be removed with remove_from_negative_keyword_list. It also explains that shared_set_id comes from create_negative_keyword_list or search.

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?