Skip to main content
Glama

add_google_negative_keywords

Add campaign-level negative keywords to a live Google Ads campaign.

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": {
      "campaignId": "<campaignId>",
      "keywords": "<keywords>"
    },
    "name": "add_google_negative_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYes
campaignIdYes
customerIdNo
loginCustomerIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It conveys that this mutates a real ad account ("live Google Ads campaign"), but says nothing about permissions/auth requirements, whether duplicate keywords are rejected or merged, whether additions are reversible, or what the call returns on partial failure.

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?

A single well-formed sentence with no filler, and the platform/scope constraint is front-loaded. It is lean to the point of being undersized for a four-parameter mutation tool, but nothing in it is wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write operation against a live ad account with no annotations, no output schema, and zero parameter documentation, one sentence is not enough. An agent can guess the intent but lacks the operational detail needed to call it correctly on the first try.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema supplies no meaning for any of the four parameters. The description only loosely maps to campaignId and keywords; it never explains customerId vs. loginCustomerId (a common source of Google Ads API errors) or what matchType does and what the default is when omitted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (add), resource (negative keywords), scope (campaign-level) and platform (Google Ads), which is enough for an agent to identify the operation immediately. It stops short of naming how it relates to any sibling tool, but no sibling covers negative keywords, so the gap is minor.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives, and no prerequisites are stated. The word "live" hints that the campaign must already exist in Google Ads, but the description never says so explicitly or explains what happens if the campaign is a draft.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources