Skip to main content
Glama

google_ads_keywords_add

Add one or more keywords to a single ad group in Google Ads. Returns the created criterion IDs; duplicate text and match type pairs are rejected.

Instructions

Adds one or more keyword criteria to a single ad group. Returns the created criterion_ids keyed by their input position. Mutating, reversible via rollback_apply (rollback pauses the keywords rather than removing them). Duplicate text+match_type pairs inside the same ad group are rejected by Google Ads — call google_ads_keywords_cross_adgroup_duplicates first if you are adding at scale.

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_idYesTarget ad group ID. All keywords in this call are added to this single ad group.
keywordsYesKeywords to add. Each item has `text` (required) and optional `match_type` (BROAD / PHRASE / EXACT, default BROAD).
Behavior4/5

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

Discloses mutating nature, reversibility via rollback_apply (with note that rollback pauses, not removes), and duplicate behavior within ad group. Annotations absent, so description carries the burden well.

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?

Three concise sentences: action/return, rollback behavior, duplicate warning. Front-loaded, no extraneous text.

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?

Comprehensive for a 3-param tool: covers return value, rollback edge case, and prerequisite check, even without output schema.

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. Description adds context about customer_id fallback, ad_group_id targeting, and keyword text/match_type details, enhancing understanding 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?

Clearly states it adds keyword criteria to a single ad group and returns the created criterion_ids. Distinguished from siblings like keywords_pause and keywords_remove.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Advises to run google_ads_keywords_cross_adgroup_duplicates first for bulk additions to avoid Google Ads duplicate rejection, providing actionable 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