Skip to main content
Glama

google_ads_monitoring_zero_conversions

Diagnose Google Ads campaigns with zero conversions by analyzing tracking, bidding, funnel, delivery, and search term quality. Returns issues and recommended actions.

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?

With no annotations, the description carries full burden. It declares read-only behavior, hardcodes the evaluation window to LAST_7_DAYS, and details the output structure. It does not mention potential side effects or rate limits, but for a diagnostic tool the disclosure is adequate.

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 detailed but well-structured, starting with purpose and output structure, then usage guidance. It is front-loaded and each sentence adds value. Slightly long but necessary for the complex output.

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, the description provides the full output structure, including nested fields and possible statuses. It also clarifies the hardcoded window and read-only nature. This is comprehensive for a diagnostic tool.

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 coverage is 100%, and the schema descriptions already capture the parameters' meaning (customer_id fallback, campaign_id required). The description adds no additional parameter-level information 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?

The description clearly states the tool diagnoses a Google Ads campaign not acquiring conversions, listing the components analyzed (tracking, bidding, funnel, delivery, search terms). It distinguishes from siblings by naming alternative tools for CPA and CV-count monitoring.

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 says when to use it (campaign with zero conversions) and provides alternatives ('For CPA monitoring use google_ads_monitoring_cpa_goal; for CV-count monitoring use google_ads_monitoring_cv_goal'). It also notes the tool is read-only and generates an action plan without execution.

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