Skip to main content
Glama
logly

mureo

by logly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

google_ads_recommendations_apply

Apply a Google Ads recommendation by its resource name to immediately commit changes like new keywords or bid strategy switches. Use after listing recommendations; changes are irreversible.

Instructions

Apply one Google Ads recommendation by resource name. Returns {resource_name} of the applied recommendation. Mutating — the underlying change (new keyword, ad copy, bidding strategy switch, etc.) is committed to the campaign immediately and is NOT reversible through this tool. The resource_name format 'customers//recommendations/' is re-validated server-side to prevent injection. To list candidates use google_ads_recommendations_list; some recommendation types also change budget, device, or schedule settings.

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.
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.
resource_nameYesRecommendation resource name exactly as returned by google_ads_recommendations_list (format: 'customers/<cid>/recommendations/<rid>'). Re-validated against a strict regex before submission.

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.37
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv0.10.11
  4. Removedv0.10.9
  5. Addedv0.9.12
  6. Removedv0.9.6
  7. Addedv0.9.2
  8. Removedv0.9.1
  9. Addedv1.0.5

TDQS

A4.5/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 does so thoroughly. It discloses that the operation is mutating, commits immediately, is not reversible through this tool, and can affect budget/device/schedule settings depending on recommendation type. It also notes server-side re-validation for injection prevention, adding valuable context beyond 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?

Four sentences, all dense with relevant information, with the core action front-loaded. Every sentence earns its place: what it does, what it returns, mutability/reversibility, resource_name format, and the listing alternative.

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 mutating tool with no output schema, the description is complete: it defines the action, return value, side effects, non-reversibility, parameter source/format, and even notes additional settings affected. Nothing an agent needs to invoke it correctly 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 the baseline is 3. The description adds some useful context—resource_name should be 'exactly as returned by google_ads_recommendations_list' and is re-validated—but largely reinforces what the schema already states, without significantly expanding param semantics.

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: 'Apply one Google Ads recommendation by resource name.' It also names the returned value and the exact resource_name format, making the tool's purpose unmistakable and clearly distinct from sibling tools like google_ads_recommendations_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly points to google_ads_recommendations_list as the way to find candidates, and warns that changes are immediately committed and not reversible through this tool. It does not explicitly name alternative tools like rollback_apply for reversibility, but the guidance is sufficient for the primary use case.

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