Skip to main content
Glama

google_ads_campaigns_create

Create a new Search or Display campaign in your Google Ads account with a specified bidding strategy and channel type. Requires an existing budget ID; create one first if needed.

Instructions

Creates a new Search or Display campaign in the specified Google Ads account. Returns the new campaign's resource_name and id. Mutating — counts against daily write quota. Reversible via rollback_apply (reversal pauses the campaign rather than deleting it). Requires a pre-existing budget_id; to create a budget first, call google_ads_budget_create. For later edits use google_ads_campaigns_update or google_ads_campaigns_update_status.

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.
nameYesCampaign name (max 255 chars). Must be unique within the account.
bidding_strategyNoGoogle Ads bidding strategy. Defaults to MAXIMIZE_CLICKS when omitted. TARGET_CPA / TARGET_ROAS require additional target fields that this tool does not expose — use the Google Ads UI or a follow-up campaigns.update for those.
budget_idNoExisting campaign-budget ID to attach. Create one first with google_ads_budget_create if you do not have one.
channel_typeNoAdvertising channel. SEARCH (default) for text ads on Google Search; DISPLAY for image/banner ads on the GDN.
Behavior4/5

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

Discloses mutating nature, write quota impact, and reversal behavior. With no annotations, it covers key behavioral aspects but lacks details on auth or error handling.

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?

Four focused sentences front-load the primary action and return, then cover mutation, prerequisites, and alternatives. No filler.

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?

Despite no output schema, the description explains return fields (resource_name, id), prerequisites, behavioral notes, and alternative tools. Covers all essential aspects for a creation tool.

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?

Adds significant context beyond the schema: default values for bidding_strategy and channel_type, and limitations on TARGET_CPA/TARGET_ROAS. The budget_id prerequisite is highlighted.

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 it creates a Search or Display campaign, specifying the resource and action. It distinguishes itself from sibling tools like update and list tools by focusing on creation.

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 states prerequisite (budget_id) and directs to google_ads_budget_create if needed. Provides alternatives for later edits (update/update_status) and mentions reversibility via rollback_apply.

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