Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_ads_create

Creates a Responsive Search Ad in a Google Ads search ad group from 3–15 headlines and 2–4 descriptions, returning the new ad's ID and approval status. Use it to launch or test search creatives, not display banners.

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 — not automatically reversible; record before-state with mureo_state_action_log_append if you may need to roll back. 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

NameRequiredDescriptionDefault
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.
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_urlNoLanding page URL the ad links to. Must match the campaign's allowed domains and be HTTPS.
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.
ad_group_idYesParent ad group ID. Must belong to a SEARCH campaign; DISPLAY ad groups reject RSAs.
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 for the RSA. 2 to 4 accepted; each description is max 90 characters display width.
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. Addedv1.0.5

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does: it declares the call mutating, not automatically reversible, prescribes recording before-state, and explains that the returned approval_status is usually UNDER_REVIEW for ~1 business day. It also flags the silent tracking-identity refusal, which is exactly the kind of non-obvious behavior an agent cannot infer from the schema.

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?

Five sentences, front-loaded with the core action and return shape, then mutation/rollback risk, then format constraints, then the sibling redirect. Each sentence carries distinct, actionable information with no filler.

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 12-parameter mutating tool with nested objects, no annotations and no output schema, the description supplies everything the structured data lacks: what is returned, the review-state delay, irreversibility, and the rollback workflow. Nothing essential to correct invocation 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%, so parameters like path1/path2, final_url, customer_id and acknowledge_tracking_findings are already documented in structured fields. The description's mentions of 3–15 headlines and 2–4 descriptions merely restate minItems/maxItems already in the schema, so it adds little beyond the baseline.

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?

States a specific verb and resource ("Creates a Responsive Search Ad (RSA)") plus the placement scope ("in the specified ad group"). The final sentence explicitly separates it from the display-ads sibling, so an agent can pick the right creative tool 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?

Names the alternative (google_ads_ads_create_display) and the condition that selects it ("For display/banner ads"), and warns the formats are not interchangeable. It also routes the agent to mureo_state_action_log_append when rollback may be needed and states the SEARCH-campaign requirement for the parent ad group.

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