Skip to main content
Glama

google_ads_ads_create

Create a Responsive Search Ad (RSA) in a specified ad group. Provide 3-15 headlines and 2-4 descriptions; returns ad ID, resource name, and approval status.

Instructions

Creates a Responsive Search Ad (RSA) in the specified ad group. Returns the new ad's resource_name, id, and initial approval_status (usually UNDER_REVIEW for ~1 business day). Mutating, reversible via rollback_apply (rollback pauses the ad). Google Ads requires 3–15 headlines and 2–4 descriptions. For display/banner ads use google_ads_ads_create_display instead; the two creative formats are not interchangeable.

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.
ad_group_idYesParent ad group ID. Must belong to a SEARCH campaign; DISPLAY ad groups reject RSAs.
headlinesYesHeadlines for the RSA. Google Ads accepts 3 to 15; each headline is max 30 characters display width. Supply at least 5 for good learning.
descriptionsYesDescriptions for the RSA. 2 to 4 accepted; each description is max 90 characters display width.
final_urlNoLanding page URL the ad links to. Must match the campaign's allowed domains and be HTTPS.
path1NoFirst URL display path (shown after the domain). Max 15 characters display width. Optional.
path2NoSecond URL display path. Max 15 characters display width. Requires path1 if set. Optional.
Behavior4/5

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

With no annotations, the description discloses mutability, reversibility via rollback_apply, and initial approval status. It adds useful behavioral context beyond bare minimum, though could mention failure modes or rate limits.

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?

The description is concise (4 sentences) with no redundancy. It front-loads the main purpose and layers additional details efficiently.

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?

Given 7 parameters and no output schema, the description covers creation constraints, return values, reversibility, and alternative tool. Missing output schema but mentions what is returned. Adequately complete for agent usage.

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?

Schema coverage is 100%, providing baseline 3. The description adds extra context like character limits for headlines/descriptions/paths and a tip to supply at least 5 headlines. These enrich parameter understanding.

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 Responsive Search Ad (RSA) in a specified ad group, using specific verbs and resource names. It distinguishes from the sibling tool google_ads_ads_create_display for display ads.

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 says when to use google_ads_ads_create_display instead, and implies use for search campaigns. Provides constraints like headline/description counts and display width limits.

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