Skip to main content
Glama

google_ads_monitoring_cpa_goal

Measures a campaign's last-7-day CPA against a target, integrating cost-increase analysis and surfacing top wasteful terms for actionable insights.

Instructions

Evaluate a Google Ads campaign's last-7-days CPA against a user-supplied target and integrate cost-increase analysis. Returns {campaign_id, target_cpa, current_cpa (float or None when conversions==0), cost_analysis (full google_ads_cost_increase_investigate payload), wasteful_terms (top 5 zero-CV cost terms from cost_analysis), deviation_pct, status ('healthy' when current<=target, 'warning' when <=target1.2 or when CV==0, 'critical' when >target1.2), issues:[strings], summary, suggested_workflow?}. The CPA window is hardcoded to LAST_7_DAYS. Read-only; does not change bids. For account-wide rollup use google_ads_health_check_all; for daily CV-count vs target 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.
target_cpaYesTarget cost per acquisition in account currency (e.g. 3000 = ¥3,000). Required — this tool does NOT fall back to bidding-strategy or actual CPA. 'warning' threshold is target_cpa * 1.2; above that is 'critical'.
Behavior5/5

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

With no annotations, description fully discloses hardcoded LAST_7_DAYS window, read-only status, and detailed return structure including status conditions. No contradictions.

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?

Description is well-structured: main purpose first, then return format, then behavioral notes and sibling references. Every sentence adds value with no redundancy.

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?

Despite no output schema, description fully defines return fields and status logic. With 100% schema coverage, no annotations, and clear sibling references, it provides all necessary context for correct invocation.

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%, so baseline 3. Description adds no new parameter semantics beyond the schema; the threshold logic is part of output behavior, not parameter meaning.

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?

Clearly states the tool evaluates a campaign's last-7-days CPA against a user target and integrates cost-increase analysis. Explicitly distinguishes from sibling tools google_ads_health_check_all and google_ads_monitoring_cv_goal.

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?

Provides explicit alternative tools for different use cases (account-wide rollup or daily CV-count). Also notes read-only nature and hardcoded window, guiding appropriate usage.

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