Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

google_ads_ads_create_display

Create a Responsive Display Ad in a DISPLAY campaign ad group. Automatically uploads marketing, square, and logo images from local paths before composing the ad. Requires ad group in a DISPLAY campaign; fails on channel mismatch.

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, reversible via rollback_apply. 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
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_idYesAd group ID. Must belong to a DISPLAY campaign.
headlinesYesShort headlines (1 to 5). Each max 30 characters display width.
long_headlineYesLong headline (max 90 characters display width). Required by Google Ads even when headlines are supplied.
descriptionsYesDescriptions (1 to 5). Each max 90 characters display width.
business_nameYesAdvertiser / business name shown in the ad (max 25 characters display width). 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.
logo_image_pathsNoOptional local file paths for logo images (up to 5). Uploaded automatically. Helps ad quality but not required.
final_urlYesLanding page URL. Must be HTTPS and match the campaign's allowed domains.

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

The description discloses that image paths are local files uploaded by mureo, returns resource_name, id, and asset IDs, and that it is mutating but reversible. It does not cover rate limits or detailed error scenarios, but overall provides good behavioral context.

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 (3-4 sentences) and well-structured: purpose first, then upload details, return info, reversibility, and disambiguation/error condition. No unnecessary words.

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 the tool's complexity (10 params, no output schema), the description covers essential aspects: creation process, image handling, return values, reversibility, and error condition. It could detail non-required parameters slightly more, but it's largely sufficient.

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%, setting a baseline of 3. The description adds value by explaining that image paths are local and uploaded automatically, grouping image types with aspect ratios, and describing the return structure beyond the 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 the purpose: 'Creates a Responsive Display Ad (RDA) in a DISPLAY campaign's ad group.' It specifies the tool's scope and differentiates from sibling 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?

The description explicitly states when to use (for DISPLAY campaigns) and when not (use google_ads_ads_create for Search). It also warns that the ad group must belong to a DISPLAY campaign, else a channel-mismatch error occurs, 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