Skip to main content
Glama
johnoconnor0

Google Ads MCP Server

by johnoconnor0

google_ads_bulk_add_keywords

Bulk add keywords to a Google Ads ad group under a single match type and optional CPC bid to streamline campaign setup.

Instructions

Bulk add multiple keywords with the same match type.

Args: customer_id: Customer ID (without hyphens) ad_group_id: Ad group ID keyword_texts: List of keyword text strings match_type: Match type for all keywords (EXACT, PHRASE, or BROAD, default: PHRASE) cpc_bid: Optional CPC bid for all keywords in currency units

Returns: Success message

Example: keyword_texts = ["running shoes", "athletic shoes", "sport shoes"]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes
ad_group_idYes
keyword_textsYes
match_typeNoPHRASE
cpc_bidNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so the description carries full burden. It states it 'adds' keywords but omits important behavioral traits like idempotency, duplicate handling, permission needs, or side effects. For a mutation tool, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with Args, Returns, and Example sections. The example is minimal but relevant. No unnecessary sentences, though could be more streamlined.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given numerous sibling tools, the description does not differentiate from 'batch_add_keywords' or 'add_keywords.' Output schema exists but is not leveraged to describe return values, leaving agent uninformed about success details.

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 description coverage is 0%, but the description adds value by listing allowed match types, default, and optional bid. However, it lacks format constraints for IDs and keyword texts, limiting completeness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Bulk add multiple keywords with the same match type,' specifying the action and resource. However, it does not differentiate from the sibling tool 'batch_add_keywords,' which likely performs a similar function, reducing clarity.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'add_keywords' or 'batch_add_keywords.' Missing prerequisites or exclusions, leaving the agent to infer context.

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/johnoconnor0/google-ads-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server