Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_ads_create_display

Creates a Responsive Display Ad in a DISPLAY campaign ad group and automatically uploads local marketing, square, and logo images as assets before composing the ad.

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

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.
approvalNoExternal approval this change carries out (recorded and shown, never verified)
expectedNoExpected effects [{metric, direction, target?, horizon_days?, primary?}], exactly one primary:true when several; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold.
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.
decision_idNoA proposed decision this change carries out.
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.33.0
    • changedInput schema / properties / expected / description
      Previous value: -"Expected effects [{metric, direction, target?, horizon_days?}]; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold."New value: +"Expected effects [{metric, direction, target?, horizon_days?, primary?}], exactly one primary:true when several; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold."
  2. Changed1 schema field changedv0.28.0
    • addedInput schema / properties / approval
      Added value: +{
+  "additionalProperties": false,
+  "description": "External approval this change carries out (recorded and shown, never verified)",
+  "properties": {
+    "approved_at": {
+      "maxLength": 64,
+      "type": "string"
+    },
+    "approved_by": {
+      "maxLength": 80,
+      "type": "string"
+    },
+    "reference": {
+      "maxLength": 128,
+      "type": "string"
+    }
+  },
+  "required": [
+    "reference",
+    "approved_by",
+    "approved_at"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changedv0.26.0
    • addedInput schema / properties / decision_id
      Added value: +{
+  "description": "A proposed decision this change carries out.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / expected
      Added value: +{
+  "description": "Expected effects [{metric, direction, target?, horizon_days?}]; metric cpa/cpc/cpl/cpm/conversions/cvr/ctr/roas/cost/spend/clicks/impressions; direction up/down/hold.",
+  "maxItems": 12,
+  "type": "array"
+}
  4. 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"
+}
  5. 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"
+}
  6. Changed1 schema field changedv0.10.37
    • addedInput schema / additionalProperties
      Added value: +false
  7. Addedv0.10.11
  8. Removedv0.10.9
  9. Addedv0.9.12
  10. Removedv0.9.6
  11. Addedv0.9.2
  12. Removedv0.9.1
  13. Addedv0.2.1
  14. Removedv0.8.0
  15. Addedv0.3.1
  16. Removedv0.3.0
  17. 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 present, the description carries the full burden and does so: it declares the call mutating, explicitly not automatically reversible, names the rollback companion (mureo_state_action_log_append), and discloses a hidden side effect (files are uploaded as ImageAsset before the ad is composed). It also names the concrete failure mode (channel mismatch) — exactly the context an agent needs before a write.

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?

Four dense sentences ordered by importance: what it creates, the file-upload side effect, return values, then mutation/rollback risk, then sibling routing and the hard precondition. No filler and no repetition of schema content.

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 15-parameter, nested-object mutation with no output schema, the description supplies what the structured data cannot: that it returns resource_name/id/asset IDs, that it is irreversible, and how to roll back. Nothing an agent needs to call it safely is missing.

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% across 15 params, so the schema already explains semantics, limits, and the tracking acknowledgment. The description adds only the sequencing detail that image paths are uploaded as ImageAsset before ad composition, which is largely restated in the schema. Baseline 3 applies.

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?

Names a specific verb + resource + variant: creating a Responsive Display Ad inside a DISPLAY campaign's ad group. It explicitly distinguishes itself from the sibling google_ads_ads_create (Search), so an agent can route correctly without opening either schema.

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?

Gives an explicit alternative ('For Search campaigns use google_ads_ads_create') and a precondition that selects the tool ('the ad_group must belong to a DISPLAY campaign or this call fails with a channel-mismatch error'). Both when-to-use and when-not-to-use are stated.

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