Skip to main content
Glama

google_ads_negative_keywords_add_to_ad_group

Add ad group-level negative keywords to exclude searches from triggering ads in a specific ad group. Supply keyword text and optional match type for precise control.

Instructions

Adds one or more ad group-level negative keywords. Scope is narrower than campaign-level negatives — exclusions apply only to the specified ad group. Returns created criterion_ids. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. Prefer this over google_ads_negative_keywords_add when the exclusion is only wrong in one ad group's context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordsYesNegative keywords to add. Each item has `text` and optional `match_type` (BROAD / PHRASE / EXACT).
ad_group_idYesAd group that will receive the negatives. Exclusions do not cascade to sibling ad groups.
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.
Behavior4/5

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

Discloses mutating nature, non-reversibility, and suggests recording before-state. Mentions return of criterion_ids. Lacks permission requirements or limits, but strong for missing annotations.

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?

Four sentences, front-loaded with main action, includes usage guideline and behavioral warning. No wasted words.

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?

Provides purpose, usage guidance, behavioral caveat, return value, and alternative reference. Complete for a 3-param tool with no output schema.

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%; description does not add meaning beyond schema. 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?

Clear verb ('Adds') and resource ('ad group-level negative keywords'). Explicitly distinguishes from campaign-level negatives and sibling tool google_ads_negative_keywords_add.

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?

States when to prefer this tool over the sibling (when exclusion only applies to one ad group). Also clarifies scope difference.

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