Skip to main content
Glama

google_ads_monitoring_zero_conversions

Diagnose a Google Ads campaign with no conversions by checking tracking, bidding, funnel, delivery, and search terms. Returns status, issues, and prioritized actions to fix it.

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

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

No annotations are provided, so the description carries the full burden. It explicitly states 'Read-only; generates an action plan but does not execute anything' and 'The evaluation window is hardcoded to LAST_7_DAYS.' It also discloses null behavior for search_term_quality when clicks==0, which is valuable behavioral context beyond the tool name.

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 long due to the detailed return object, but it is front-loaded with the purpose and every major section (output shape, hardcoded window, read-only, alternatives) earns its place. It is dense but structured with clear field names, though it could be slightly more scannable.

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?

This is a complex diagnostic tool with no output schema and no annotations, yet the description includes the full return structure, status enum, null condition, hardcoded period, and related tool pointers. It is nearly self-sufficient for an agent to invoke correctly and interpret the result.

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?

Input schema has 100% parameter description coverage; campaign_id and customer_id are both fully described with examples and fallback behavior. The description itself adds no additional parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Diagnose a Google Ads campaign that is not acquiring conversions' and enumerates the diagnostic dimensions (tracking config, bidding alignment, funnel, delivery, search terms). It also explicitly distinguishes itself from sibling tools by naming google_ads_monitoring_cpa_goal and google_ads_monitoring_cv_goal as alternatives.

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 provides clear usage context: hardcoded LAST_7_DAYS window, read-only behavior, and explicit alternatives for CPA and CV-count monitoring. This tells the agent when to use this tool and when to use a different one.

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