Skip to main content
Glama

google_ads_cpc_detect_trend

Analyze CPC trends in a Google Ads campaign using daily segmentation and linear regression. Returns trend direction, slope, and insights on week-over-week surges and outlier days.

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?

Although no annotations are provided, the description fully discloses behavioral traits: it is read-only, excludes days with zero clicks, defines thresholds for direction detection (rising >+1%, falling <-1%), and describes insight generation (week-over-week surges, 2x average CPC). The return structure is detailed, including optional fields. 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?

A single well-structured paragraph that fronts the main action and immediately describes the return structure. Every sentence adds value, with no filler. The use of parentheses, question marks for optional fields, and colons for nesting makes it parseable.

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, the description fully documents the return format (campaign details, daily data, trend object with slope and thresholds, insights list) and edge cases (insufficient_data direction, optional change_rate_per_day_pct). All three parameters are adequately covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema coverage is 100%, but the description adds significant meaning beyond schema: explains fallback behavior for customer_id, provides usage context for period enum values (e.g., when to use LAST_7_DAYS vs LAST_90_DAYS), and clarifies campaign_id provenance. This exceeds the baseline of 3.

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 starts with 'Detect rising/falling CPC trends', which is a specific verb and resource. It explicitly distinguishes itself from sibling tools by naming alternatives (google_ads_device_analyze, google_ads_auction_insights_analyze) for different investigation types.

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 when-to-use context (diagnosing CPC trends) and when-not-to (for device or auction-share issues), with named alternatives. Also advises on period selection: short windows for recent changes, long windows for baselines.

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