Google Ads - AdLoop

Overview Schema Source Related Servers Discussions Admin

Draft additions to a negative keyword list

add_to_negative_keyword_list

Append new keywords to an existing shared negative keyword list in Google Ads. Validate current list contents to avoid duplicates, then use the returned plan to confirm and apply changes.

Instructions

Append keywords to an EXISTING shared negative keyword list — returns a PREVIEW.

Use this when a suitable list already exists and only needs more keywords (instead of propose_negative_keyword_list, which creates a new list). Always call get_negative_keyword_lists first to find the right shared_set_id and get_negative_keyword_list_keywords to avoid duplicating existing terms.

shared_set_id: numeric ID from get_negative_keyword_lists (shared_set.id). keywords: list of keyword strings to append (duplicates in the input list are collapsed). match_type: "EXACT", "PHRASE", or "BROAD"

Call confirm_and_apply with the returned plan_id to execute.

Input Schema

TableJSON Schema

Name	Required	Default
`keywords`	Yes
`match_type`	No	EXACT
`customer_id`	No
`shared_set_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.13.2Sep 7, 2026
Removedv0.13.0Jul 22, 2026
First observedv0.9.0Jun 19, 2026

TDQS

A4.1/5.0

Behavior1/5

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

Description says tool returns a preview and requires confirm_and_apply to execute, implying it does not directly modify state. However, annotations declare readOnlyHint: false, which contradicts this by suggesting it does modify. This inconsistency undermines transparency.

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?

Well-organized with separate lines for purpose, usage, parameters, and next step. No redundant info; concise and scannable.

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?

Covers purpose, usage, prerequisites, parameter details, and the workflow with confirm_and_apply. Also mentions related get_tools. Complete for effective use.

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?

Explains shared_set_id, keywords, and match_type with values, but omits explanation for customer_id. However, most parameters are well described, adding context beyond schema.

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?

Clearly states the verb 'Append', object 'keywords to an EXISTING shared negative keyword list', and distinguishes from creating a new list. Includes explicit use case.

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?

Explicitly states when to use this tool versus propose_negative_keyword_list, and instructs to first call get_negative_keyword_lists and get_negative_keyword_list_keywords to avoid duplication. Also mentions follow-up action confirm_and_apply.

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

Deploy Server