Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_ads_create

Create a Responsive Search Ad in a specified Google Ads search ad group and get its resource name, ID, and initial approval status. Supply 3–15 headlines and 2–4 descriptions to submit the ad for review.

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

TableJSON 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.
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.
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.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. 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 disclosure burden, and it meets it: it flags the operation as 'Mutating — not automatically reversible,' suggests recording a before-state for rollback, and reveals the likely post-create approval_status and its ~1 business day timing. This is the kind of outside-the-schema behavior an agent needs to know.

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 each earn their place: action/return, reversibility, validity constraints, and sibling routing. The most decision-relevant information is 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?

Although there is no output schema and no annotations, the description explicitly names the returned fields (resource_name, id, approval_status), warns about non-reversibility, and covers the format constraints and main alternative. Combined with the fully described input schema, nothing critical is left for an agent to guess.

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?

The schema covers every parameter with descriptive text (100% coverage), so the baseline is 3. The description's mention of '3–15 headlines and 2–4 descriptions' restates the schema's min/max constraints rather than adding new field-level meaning.

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 opens with a specific action and object: 'Creates a Responsive Search Ad (RSA) in the specified ad group.' It also distinguishes the tool from the sibling display-ad creator, so an agent can disambiguate without opening the 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?

It explicitly tells the agent when to use the sibling tool instead: 'For display/banner ads use google_ads_ads_create_display instead; the two creative formats are not interchangeable.' It also states the mandatory headline/description counts, which serve as preconditions for calling this tool.

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