Skip to main content
Glama

google_ads_keywords_add

Add one or more keywords to a single Google Ads ad group. Specify ad_group_id and keyword text with optional match type (BROAD, PHRASE, EXACT). Returns created criterion IDs keyed by input position.

Instructions

Adds one or more keyword criteria to a single ad group. Returns the created criterion_ids keyed by their input position. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. 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
keywordsYesKeywords to add. Each item has `text` (required) and optional `match_type` (BROAD / PHRASE / EXACT, default BROAD).
ad_group_idYesTarget ad group ID. All keywords in this call are added to this single ad group.
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?

No annotations provided, so description fully defines behavior. Clearly states the tool is mutating and not automatically reversible, advises recording state. Explains duplicate rejection by Google Ads. Lacks explicit permission or rate limit details but covers key traits 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?

Two concise sentences with critical information front-loaded. No wasted words, each sentence provides necessary guidance.

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?

With 3 parameters and 100% schema coverage, description covers return format (criterion_ids keyed by position), duplicate handling, rollback suggestion, and cross-tool dependency. Complete for a keyword add tool with no 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%, and description adds value beyond schema: clarifies customer_id fallback, text max length of 80 chars/10 words, match type default BROAD, and that bracketed forms should not be used in text field. Adds meaningful context for correct parameter usage.

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 states 'Adds one or more keyword criteria to a single ad group' with a clear verb and resource. It distinguishes from sibling tools like list, pause, remove, and cross_adgroup_duplicates.

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 call google_ads_keywords_cross_adgroup_duplicates first when adding at scale to avoid duplicate rejections, and recommends recording before-state with mureo_state_action_log_append for rollback. Provides clear when-to-use and when-not-to 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