Skip to main content
Glama

google_ads_ad_groups_create

Create a new ad group in an active or paused Google Ads campaign to organize ads and keywords. Returns the ad group's resource name and ID for further actions.

Instructions

Creates a new ad group inside an existing campaign. Returns the new ad_group's resource_name and id. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. The parent campaign must be ENABLED or PAUSED; creating under a REMOVED campaign fails. After creation, add ads with google_ads_ads_create and keywords with google_ads_keywords_add.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAd group name (max 255 chars). Must be unique within the parent campaign.
campaign_idYesParent campaign ID. Must exist and not be REMOVED.
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.
cpc_bid_microsNoDefault CPC bid in micros (1 JPY = 1_000_000 micros; 1 USD = 1_000_000 micros). Minimum 10_000 (= ¥0.01 / $0.01). Omit to inherit the campaign's default.
Behavior5/5

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

With no annotations, the description carries the full burden. It discloses that the operation is mutating, not automatically reversible, suggests rollback via mureo_state_action_log_append, and states the campaign status precondition. This is exemplary behavioral disclosure.

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?

Three sentences, front-loaded with the main action, then returns, mutation warning, precondition, and next steps. Every sentence carries essential information with no redundancy.

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?

For a create tool with no output schema and no annotations, the description covers creation, return values, mutation risk, rollback guidance, preconditions, and subsequent workflow. It is remarkably complete for the tool's complexity.

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 100%, so parameters are already well-documented. The description does not add new parameter-level details beyond reinforcing that the parent campaign must be active, which is already implied by the campaign_id schema description. Baseline 3 is appropriate.

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 'Creates a new ad group inside an existing campaign' with a specific verb and resource, distinguishing it from update/list siblings. It also mentions the return values, further clarifying its purpose.

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?

Provides clear context for usage: parent campaign must be ENABLED or PAUSED, and it recommends follow-up actions (add ads, keywords). However, it does not explicitly contrast with alternatives like google_ads_ad_groups_update, so a perfect score is not warranted.

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