Skip to main content
Glama
Sign In
AdLoop: Google Ads, Reddit Ads & GA4

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Draft additions to a negative keyword list

add_to_negative_keyword_list

Append keywords to an existing shared negative keyword list to block unwanted ad traffic. Returns a preview plan; confirm to apply changes.

Instructions

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

Adds terms to a list that already exists (propose_negative_keyword_list creates a new list instead); get_negative_keyword_list_keywords shows the terms already in a list. Returns a preview with a plan_id; nothing changes until confirm_and_apply applies it.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

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": {
      "shared_set_id": "<shared_set_id>",
      "keywords": "<keywords>"
    },
    "name": "add_to_negative_keyword_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesKeyword strings to append. Blank entries are dropped and duplicates in the input list are collapsed (case-insensitive).
match_typeNoMatch type applied to every keyword: "EXACT" (default), "PHRASE", or "BROAD" (case-insensitive).EXACT
customer_idNoGoogle Ads customer ID (digits, dashes optional). Defaults to the configured account.
shared_set_idYesNumeric ID of the list (shared_set.id from get_negative_keyword_lists).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.27.1
    • addedInput schema / properties / customer_id / description
      Added value: +"Google Ads customer ID (digits, dashes optional). Defaults to\nthe configured account."
    • addedInput schema / properties / keywords / description
      Added value: +"Keyword strings to append. Blank entries are dropped and\nduplicates in the input list are collapsed (case-insensitive)."
    • addedInput schema / properties / match_type / description
      Added value: +"Match type applied to every keyword: \"EXACT\" (default),\n\"PHRASE\", or \"BROAD\" (case-insensitive)."
    • addedInput schema / properties / shared_set_id / description
      Added value: +"Numeric ID of the list (shared_set.id from\nget_negative_keyword_lists)."
  2. Addedv0.13.2
  3. Removedv0.13.0
  4. First observedv0.9.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, which leaves the draft-vs-commit semantics ambiguous. The description supplies that missing context: the call is non-mutating, returns a preview with a plan_id, and requires confirm_and_apply before anything changes.

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?

Front-loaded with the core action and its preview nature in one sentence, followed by sibling routing and commit semantics. The API doc link is short and placed last; no sentence is wasted.

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?

Output schema exists so return-value detail is unnecessary, and the description still explains the plan_id concept. Combined with full schema coverage and covered sibling routing, an agent has everything needed to call this correctly.

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

Parameters3/5

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

Schema description coverage is 100% and the schema already documents match_type defaults, customer_id fallback, and blank/duplicate handling for keywords. The description adds only the notion of the target being an existing list, so baseline 3 is appropriate.

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 (append), resource (keywords in a shared negative keyword list), and hard scope constraint (EXISTING list, returns a PREVIEW). The agent can distinguish this from propose_negative_keyword_list and add_negative_keywords without opening either schema.

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 routes between siblings: propose_negative_keyword_list for creating a new list, get_negative_keyword_list_keywords for inspecting existing terms, and confirm_and_apply to actually commit the change. Both when-to-use and the required follow-up are stated.

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

Deploy Server

Other Tools