Skip to main content
Glama

google_ads_negative_keywords_add

Add campaign-level negative keywords to a Google Ads campaign, applying to all ad groups. This broad targeting may over-block; consider ad-group-level negatives for narrower exclusions.

Instructions

Adds one or more campaign-level negative keywords. These apply to every ad group in the campaign. Returns created criterion_ids. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. 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
keywordsYesNegative keywords to add. Each item has `text` and optional `match_type` (BROAD / PHRASE / EXACT; EXACT is the safest for narrow exclusions).
campaign_idYesCampaign that will receive the negatives. The negatives apply to all ad groups under this campaign.
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.
Behavior5/5

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

No annotations exist, but the description fully discloses the mutating nature, irreversibility, and need for manual rollback via mureo_state_action_log_append. Also states that keywords apply to all ad groups.

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?

Concise single paragraph with clear, front-loaded purpose. Each sentence adds value: purpose, scope, rollback warning, and sibling differentiation. No redundant information.

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, behavioral implications, parameter details, and mentions return value (criterion_ids). No output schema, but return indication is sufficient for a mutation tool.

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 coverage is 100%, baseline 3. The description adds guidance: plain text for keywords, match_type enum details, and recommends EXACT as safest. Provides extra 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?

The description clearly states the tool adds campaign-level negative keywords, specifies scope (applies to all ad groups), and differentiates from the sibling tool for ad-group scope.

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 provides when-to-use and when-not-to-use guidance: directs to google_ads_negative_keywords_add_to_ad_group for ad-group negatives and warns about potential over-blocking. Also advises recording before-state for rollback.

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