Skip to main content
Glama

google_ads_recommendations_list

Retrieve Google Ads automated recommendations for your account. Filter by campaign or recommendation type to scope results, then use returned resource names to apply them.

Instructions

List Google's current automated recommendations for the account. Returns [{resource_name, type (RecommendationType enum string, e.g. 'KEYWORD', 'TEXT_AD', 'TARGET_CPA_OPT_IN', 'MAXIMIZE_CONVERSIONS_OPT_IN'), impact:{base_metrics:{impressions, clicks, cost_micros}}, campaign_id (resource path when scoped to a campaign)}]. Read-only. Filter by campaign_id to scope to one campaign, or by recommendation_type to scope to one kind. To apply a recommendation use google_ads_recommendations_apply with resource_name from this list.

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.
campaign_idNoOptional campaign ID as a numeric string. Omit to list account-wide recommendations.
recommendation_typeNoOptional RecommendationType enum string (e.g. 'KEYWORD', 'TEXT_AD', 'TARGET_CPA_OPT_IN'). Validated against the client's allow-list before GAQL embedding.
Behavior4/5

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

Discloses read-only behavior and return structure. No annotations provided, so description carries full burden; while it lacks auth or rate limit details, it is sufficient for a list tool.

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?

Concise, front-loaded with main purpose, and no redundant information.

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?

Given no output schema, description fully covers return format and filtering options, making it complete for use.

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

Parameters5/5

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

Adds significant value beyond schema by explaining parameter defaults (customer_id falls back to credentials), scoping behavior, and filter validation.

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 it lists Google Ads recommendations and specifies the return format. It distinguishes from sibling tools like google_ads_recommendations_apply.

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 mentions read-only nature, filtering options, and directs to google_ads_recommendations_apply for applying recommendations.

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