Skip to main content
Glama

google_ads_negative_keywords_add

Add campaign-level negative keywords to a Google Ads campaign. These apply to every ad group, preventing over-blocking. Specify text and optional match type (BROAD, PHRASE, EXACT). Returns created criterion IDs.

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?

With no annotations provided, the description carries full burden. It discloses that the tool is mutating, reversible via rollback_apply, and returns created criterion_ids. However, it could mention prerequisites (e.g., campaign existence) or rate limits, but the information given is sufficient for safe use.

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?

The description is very concise, using only three sentences to convey purpose, scope, return value, mutagenicity, alternative usage, and a caution. No fluff, every sentence adds value.

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?

Given the moderate complexity of the tool (3 params, no output schema), the description covers key aspects: action, scope, return, and sibling alternative. It could mention validation or limits, but the provided context is adequate for selection and invocation.

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 coverage is 100%, so baseline is 3. The description adds minor guidance (e.g., 'EXACT is the safest for narrow exclusions') but mostly rephrases schema info. It does not significantly enhance understanding beyond what the schema already provides.

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 that the tool adds campaign-level negative keywords, specifies they apply to every ad group, and explicitly distinguishes the sibling tool for ad-group-level negatives. The purpose is specific and unambiguous.

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?

The description provides explicit guidance on when to use this tool versus the alternative (google_ads_negative_keywords_add_to_ad_group) and warns about over-blocking risk, making it easy for the agent to choose correctly.

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