Skip to main content
Glama

google_ads_negative_keywords_add_to_ad_group

Add ad group-level negative keywords to exclude specific search queries from triggering ads, with match type control (Broad, Phrase, Exact). Ideal when exclusions apply only to one ad group.

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

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

Discloses mutating nature, reversibility via rollback_apply, and returns created criterion_ids. No annotations provided, so description carries full burden and does so thoroughly.

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 concise sentences, front-loaded with purpose, followed by scope, behavior, and usage advice. No extraneous content.

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, scope, behavior (mutation, reversibility), return value (criterion_ids), and usage guidance. Adequate for agent decision-making given 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 covers 100% of parameters with descriptions. Tool description adds minimal param-specific info beyond schema (e.g., output mention). Baseline 3 as schema already handles parameter semantics well.

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?

Clearly states it adds ad group-level negative keywords, distinguishing from campaign-level negatives (google_ads_negative_keywords_add). Uses specific verb 'adds' and resource 'ad group-level negative keywords'.

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 advises to prefer this tool over google_ads_negative_keywords_add when exclusion is only relevant in one ad group context. Provides clear scope comparison.

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