Skip to main content
Glama

google_ads_ads_create_display

Creates a Responsive Display Ad in a DISPLAY campaign's ad group by uploading local marketing and square images as ImageAssets, then composing the ad. Returns the new ad's resource name, ID, and generated asset IDs.

Instructions

Creates a Responsive Display Ad (RDA) in a DISPLAY campaign's ad group. Marketing/square/logo image paths point to local files; mureo uploads each file to Google Ads as an ImageAsset before composing the ad. Returns the new ad's resource_name, id, and the generated asset IDs. Mutating — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. For Search campaigns use google_ads_ads_create; the ad_group must belong to a DISPLAY campaign or this call fails with a channel-mismatch error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
final_urlYesLanding page URL. Must be HTTPS and match the campaign's allowed domains.
headlinesYesShort headlines (1 to 5). Each max 30 characters display width.
ad_group_idYesAd group ID. Must belong to a DISPLAY campaign.
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.
descriptionsYesDescriptions (1 to 5). Each max 90 characters display width.
business_nameYesAdvertiser / business name shown in the ad (max 25 characters display width). Required.
long_headlineYesLong headline (max 90 characters display width). Required by Google Ads even when headlines are supplied.
logo_image_pathsNoOptional local file paths for logo images (up to 5). Uploaded automatically. Helps ad quality but not required.
marketing_image_pathsYesLocal file paths for landscape marketing images (1.91:1 ratio). 1 to 15 accepted; 3+ strongly recommended for delivery quality. mureo uploads the files automatically before creating the ad.
square_marketing_image_pathsYesLocal file paths for square marketing images (1:1 ratio). 1 to 15 accepted; 3+ recommended. Uploaded automatically.
Behavior5/5

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

Despite no annotations, the description fully discloses mutating nature, non-reversibility, image upload process, and failure conditions. No contradiction.

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 and informative, though slightly lengthy. It front-loads the main purpose and provides necessary details without 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?

Covers purpose, usage, behavior, parameter guidance, and return values. Lacks output schema but description fills the gap by stating what is returned (resource_name, id, asset IDs).

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 covers all parameters with descriptions; the description adds value by explaining the automatic file upload and recommending minimum images for delivery quality.

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 Display Ad (RDA) for DISPLAY campaigns, distinguishing it from sibling tools like google_ads_ads_create for Search campaigns.

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 (DISPLAY campaign ad groups) and when not (use the sibling for Search), and warns of failure on channel mismatch. Also advises logging before-state for rollback.

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