Skip to main content
Glama
johnoconnor0

Google Ads MCP Server

by johnoconnor0

google_ads_batch_add_keywords

Add multiple keywords to Google Ads ad groups in a single batch operation. Specify ad group ID, keyword text, match type, and bid to streamline keyword management.

Instructions

Add multiple keywords in a single batch operation.

Args: customer_id: Google Ads customer ID (10 digits, no hyphens) keywords_json: JSON array of keyword configurations

Keyword Configuration Schema:

[
  {
    "ad_group_id": "12345678",
    "text": "keyword phrase",
    "match_type": "EXACT",
    "cpc_bid": 1.50
  }
]

Required Fields: ad_group_id, text Optional Fields: match_type (default: BROAD), cpc_bid Match Types: EXACT, PHRASE, BROAD

Returns: Batch operation result with success/failure details

Example: google_ads_batch_add_keywords( customer_id="1234567890", keywords_json='[{"ad_group_id": "12345678", "text": "running shoes", "match_type": "EXACT"}]' )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes
keywords_jsonYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It details required/optional fields, defaults, match types, and return format. It does not mention destructive nature or auth, but is adequate for a creation tool.

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?

Description is well-structured with sections (Args, Schema, Returns, Example) and front-loaded purpose. Slightly long due to schema reproduction but appropriate for complexity.

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

Completeness4/5

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

Complex batch operation with nested JSON; description covers input structure thoroughly. Output is described as 'result with success/failure details' which is sufficient given output schema availability (though not shown).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description fully compensates: explains customer_id format (10 digits, no hyphens) and keywords_json as a JSON array with complete sub-schema (ad_group_id, text, match_type, cpc_bid, defaults, and match type enum).

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 clearly states the function: 'Add multiple keywords in a single batch operation.' The verb 'Add' and resource 'multiple keywords' are specific, and 'batch' distinguishes it from singular add_keywords or bulk_add_keywords siblings.

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

Usage Guidelines3/5

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

The description implies batching is for efficiency, but does not explicitly state when to use this tool versus alternatives like add_keywords or bulk_add_keywords. No when-not or exclusions are provided.

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