Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_ads_create_display

Uploads local marketing and logo images, then creates a responsive display ad in a DISPLAY campaign ad group. Requires headlines, descriptions, business name, and final URL. 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
reasonNoWhy this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.
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.
acknowledge_tracking_findingsNoSet true ONLY after showing the operator a refused tracking pre-flight and getting their decision. mureo refuses the create when the final URL's tracking parameters carry another campaign's identity, because that defect is silent once live — delivery and spend stay healthy while reporting is wrong. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.20.0
    • addedInput schema / properties / reason
      Added value: +{
+  "description": "Why this change is being made: one or two sentences naming the evidence and the expected effect. Stored in the journal and on the action_log entry this call produces, for the operator and the next session.",
+  "maxLength": 500,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.10.44
    • addedInput schema / properties / acknowledge_tracking_findings
      Added value: +{
+  "description": "Set true ONLY after showing the operator a refused tracking pre-flight and getting their decision. mureo refuses the create when the final URL's tracking parameters carry another campaign's identity, because that defect is silent once live — delivery and spend stay healthy while reporting is wrong. Default false.",
+  "type": "boolean"
+}
  3. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  4. Addedv0.10.11
  5. Removedv0.10.9
  6. Addedv0.9.12
  7. Removedv0.9.6
  8. Addedv0.9.2
  9. Removedv0.9.1
  10. Addedv0.2.1
  11. Removedv0.8.0
  12. Addedv0.3.1
  13. Removedv0.3.0
  14. Addedv1.0.6

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it does so thoroughly. It discloses that the call is mutating and not automatically reversible, recommends recording before-state via mureo_state_action_log_append, explains automatic image file upload as ImageAssets, declares returned fields, and warns about the channel-mismatch failure mode.

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 four focused sentences with no filler: purpose, upload behavior, return values, and mutation/rollback warning. Each sentence earns its place and the most decision-relevant constraints are front-loaded.

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 and no annotations, the description covers the essential return values, failure conditions, rollback recommendation, and automatic upload behavior. Combined with a 100% schema-coverage input schema, nothing critical is missing for an agent to call this tool correctly.

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 the baseline is 3. The description adds useful aggregate context about local image file paths and automatic upload, but most parameter-level meaning is already fully documented in the schema, and the description does not add meaning beyond what the schema provides.

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 states a specific verb and resource: 'Creates a Responsive Display Ad (RDA) in a DISPLAY campaign's ad group.' It also explicitly distinguishes itself from the sibling google_ads_ads_create by noting that Search campaigns should use that tool, so an agent can tell them apart immediately.

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?

Usage guidance is explicit: 'For Search campaigns use google_ads_ads_create' names the alternative tool and the condition that selects it. It also warns that the ad group must belong to a DISPLAY campaign or the call fails with a channel-mismatch error, giving a clear guardrail.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools