Skip to main content
Glama

google_ads_negative_keywords_add

Add campaign-level negative keywords to exclude irrelevant search terms across all ad groups. Supports rollback for safe adjustments.

Instructions

Adds one or more campaign-level negative keywords. These apply to every ad group in the campaign. Returns created criterion_ids. Mutating, reversible via rollback_apply. For negatives scoped to a single ad group use google_ads_negative_keywords_add_to_ad_group instead — campaign-level negatives can over-block if applied too broadly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
campaign_idYesCampaign that will receive the negatives. The negatives apply to all ad groups under this campaign.
keywordsYesNegative keywords to add. Each item has `text` and optional `match_type` (BROAD / PHRASE / EXACT; EXACT is the safest for narrow exclusions).
Behavior4/5

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

Discloses mutation, reversibility via rollback_apply, and that it returns created criterion_ids. No annotations exist, so description carries the burden; it covers key aspects but could mention duplicate handling or permissions.

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?

Two concise sentences plus a clear note; no extraneous information, perfectly front-loaded.

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

Completeness4/5

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

For a 3-param tool with no output schema and no annotations, the description is fairly complete: purpose, scope, return, reversibility, and alternative. Could mention error handling or idempotency, but overall sufficient.

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 covers all parameters with descriptions. The description adds context about safest match type but does not significantly augment beyond schema, achieving baseline for high coverage.

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 clearly states it adds campaign-level negative keywords that apply to all ad groups, and distinguishes from the sibling tool for ad-group-level negatives.

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 tells when to use the sibling tool instead and warns about over-blocking with campaign-level negatives, providing clear directional guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server