Skip to main content
Glama

google_ads_monitoring_zero_conversions

Diagnose a Google Ads campaign with zero conversions by analyzing tracking setup, bidding alignment, funnel bottlenecks, delivery issues, and wasteful search terms, then generate an action plan to fix conversion acquisition.

Instructions

Diagnose a Google Ads campaign that is not acquiring conversions by composing tracking config, bidding alignment, last-7-days funnel, delivery diagnostics, and search-term quality. Returns {campaign_id, conversion_tracking:{total_actions, enabled_actions, has_issue, actions}, bidding_cv_alignment:{strategy, is_smart_bidding, cv_tracking_configured, issue}, funnel:{period:'LAST_7_DAYS', impressions, clicks, conversions, cost, ctr, cvr, bottleneck ('no_delivery'|'no_clicks'|'no_conversions'|None)}, delivery_diagnosis:{issues, warnings, recommendations}, search_term_quality:{total_terms, zero_cv_terms, zero_cv_cost, top_wasteful_terms} (null when clicks==0), status ('critical'|'warning'|'healthy'), issues:[strings], summary, suggested_workflow?, recommended_actions:[{priority, action, description}]}. The evaluation window is hardcoded to LAST_7_DAYS. Read-only; generates an action plan but does not execute anything. For CPA monitoring use google_ads_monitoring_cpa_goal; for CV-count monitoring use google_ads_monitoring_cv_goal.

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_idYesCampaign ID as a numeric string without dashes (e.g. '23743184133'). Obtain via google_ads_campaigns_list.
Behavior4/5

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

The description discloses key behavioral traits: the tool is read-only, the evaluation window is hardcoded to LAST_7_DAYS, and it returns a structured diagnosis. It also mentions that certain fields are null under specific conditions. However, it does not discuss authentication requirements or rate limits, which would be helpful for an agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized given the tool's complexity. It front-loads the purpose and then details the return structure. While some internal structure (like the list of fields) could be more concise, the description efficiently packs relevant information without unnecessary verbosity.

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?

The description is comprehensive: it explains the tool's purpose, what it evaluates, the exact return structure including nested fields and statuses, edge cases (null for certain conditions), and links to sibling tools for comparison. Since there is no output schema, the description fully carries the burden of explaining the return value.

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?

Both parameters are already fully described in the input schema with 100% coverage. The description repeats the schema's information about the customer_id fallback without adding new context. No additional semantics are provided beyond what the schema offers, meeting the baseline for high schema coverage.

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 clearly states the tool's purpose: 'Diagnose a Google Ads campaign that is not acquiring conversions' and lists the areas it covers (tracking config, bidding alignment, etc.). It distinguishes itself from sibling tools like google_ads_monitoring_cpa_goal and google_ads_monitoring_cv_goal by mentioning them as alternatives for other monitoring needs.

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?

The description explicitly states when to use this tool ('diagnose a campaign not acquiring conversions') and when not to ('For CPA monitoring use...; for CV-count monitoring use...'). It also clarifies that the tool is read-only and generates an action plan without executing anything, providing clear usage 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