Skip to main content
Glama

google_ads_cpc_detect_trend

Detect rising or falling CPC trends in a Google Ads campaign using daily segmentation and linear regression. Identify week-over-week surges and days with abnormal CPC spikes.

Instructions

Detect rising/falling CPC trends in a Google Ads campaign over a reporting window using daily segmentation and linear regression. Returns {campaign_id, campaign_name, period, data_points, daily_data:[{date, average_cpc, clicks, impressions, cost}], trend:{direction ('rising'|'falling'|'stable'|'insufficient_data'), slope_per_day, change_rate_per_day_pct? (present only when direction is not 'insufficient_data' — i.e. when at least 2 daily data points are available), avg_cpc, min_cpc, max_cpc}, insights:[strings]}. Direction is 'rising' when daily change > +1%, 'falling' when < -1%. Days with zero clicks are excluded from the GAQL. Insights call out week-over-week surges >15% and days exceeding 2x average CPC. Read-only. For device or auction-share investigation use google_ads_device_analyze or google_ads_auction_insights_analyze.

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.
periodNoReporting window for the metrics. Default 'LAST_30_DAYS'. Use a shorter window (LAST_7_DAYS / LAST_14_DAYS) when diagnosing recent changes; use LAST_90_DAYS for trend baselines.
Behavior5/5

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

The description fully discloses behavior: read-only nature, exclusion of zero-click days, direction thresholds (+1%/-1%), and insight generation. Since no annotations are provided, the description carries the full burden and does so thoroughly.

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 slightly verbose. It front-loads the core purpose and structure, then expands on thresholds and insights. Every sentence adds value, but some parts could be streamlined without losing clarity.

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 the tool has no output schema and 3 parameters, the description fully specifies the return structure (including nested objects and optional fields) and parameter details, leaving no ambiguity.

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?

Schema coverage is 100%, and the description adds meaningful context: customer_id fallback behavior, campaign_id acquisition method, and period parameter usage suggestions (e.g., short window for recent changes, long window for baselines).

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 detects rising/falling CPC trends using daily segmentation and linear regression. It specifies the return object and distinguishes from sibling tools like google_ads_device_analyze and google_ads_auction_insights_analyze.

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 explicit guidance on when to use this tool (diagnosing CPC trends) and when to use alternatives (device or auction-share analysis). It also recommends appropriate period windows for different scenarios.

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