Skip to main content
Glama
johnoconnor0

Google Ads MCP Server

by johnoconnor0

google_ads_batch_create_campaigns

Batch create multiple Google Ads campaigns with a single API call, supporting partial failures for efficient campaign management.

Instructions

Create multiple campaigns in a single batch operation.

Supports partial failure - some campaigns may succeed while others fail.

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

Campaign Configuration Schema:

[
  {
    "name": "Campaign Name",
    "type": "SEARCH",
    "status": "PAUSED",
    "budget_amount": 50.00,
    "bidding_strategy": "MAXIMIZE_CONVERSIONS",
    "target_cpa": 25.00
  }
]

Required Fields: name, budget_amount Optional Fields: type (default: SEARCH), status (default: PAUSED), bidding_strategy, target_cpa

Returns: Batch operation result with success/failure details

Example: google_ads_batch_create_campaigns( customer_id="1234567890", campaigns_json='[{"name": "Campaign 1", "budget_amount": 50}, ...]' )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customer_idYes
campaigns_jsonYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

There are no annotations, so the description carries the full burden. It discloses that the operation is a batch creation that supports partial failure, and describes the input JSON structure and defaults. It does not mention any destructive behavior, auth needs, or rate limits, but for a creation tool this is sufficient.

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?

The description is well-structured with sections (Args, Campaign Configuration Schema, Required/Optional, Example). It is a bit longer but every sentence adds value given the complexity of the JSON parameter. Front-loaded with the main purpose.

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?

Given that the tool has an output schema (so return details are not required), the description comprehensively covers input parameters, defaults, partial failure behavior, and provides a full example. It compensates for the missing schema descriptions and the complexity of batch creation.

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?

Input schema descriptions are missing (0% coverage), so the description must compensate. It provides detailed semantics: customer_id format (10 digits, no hyphens) and campaigns_json as a JSON array with a full schema including required/optional fields, defaults (type=SEARCH, status=PAUSED), and an example. This goes far beyond the bare 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?

The description clearly states 'Create multiple campaigns in a single batch operation', which is a specific verb-resource pair. It distinguishes itself from sibling tools like google_ads_create_campaign (single campaign creation) and other batch tools like google_ads_batch_create_ad_groups.

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?

The description implies batch usage and mentions partial failure, providing clear context. However, it does not explicitly state when not to use it or contrast with alternatives like sequential single creation. It also lacks prerequisites or constraints.

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