Skip to main content
Glama

google_ads_recommendations_apply

Apply a Google Ads recommendation by resource name to commit its changes (new keyword, ad copy, bidding strategy) to the campaign immediately. The change is irreversible and uses the resource name from the list tool.

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
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.
Behavior5/5

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

With no annotations, the description fully discloses the mutating nature, immediate commitment, irreversibility, and server-side validation. It also notes that some recommendation types affect budget/device/schedule.

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, each adding essential information: action/return, mutation warning, validation detail, and pointer to list tool. No wasted words.

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 simple apply tool with minimal parameters and no output schema, the description provides all necessary context: purpose, side effects, irreversibility, and how to get inputs. Complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

100% schema coverage provides parameter descriptions, but the tool description adds value by explaining the resource_name format validation and the optional customer_id fallback, enhancing understanding beyond the schema.

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?

Description clearly states 'Apply one Google Ads recommendation by resource name' with a specific verb and resource. It distinguishes itself from the sibling tool google_ads_recommendations_list which lists candidates.

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?

Explicitly directs to use google_ads_recommendations_list for listing candidates. Warns about irreversible changes and immediate commitment, providing clear when-to-use context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/logly/mureo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server