Skip to main content
Glama

google_ads_device_analyze

Compare Google Ads campaign performance across desktop, mobile, and tablet devices. Get insights on spend, conversions, CTR, and CPA ratios to identify underperforming segments.

Instructions

Compare Google Ads campaign performance across device segments (Desktop / Mobile / Tablet). Returns {campaign_id, campaign_name, period, devices:[{device_type, impressions, clicks, cost, conversions, ctr (percent), average_cpc, cpa, cvr (percent)}], insights:[strings]}, sorted by cost descending. cpa is None when conversions == 0. Insights fire for devices with spend and zero conversions, worst/best CPA ratios > 1.5x, and Mobile CTR less than half of Desktop CTR. Read-only. Returns a 'message' field and empty devices list when no device-segmented data exists. For applying device bid modifiers use google_ads_bid_adjustments_update or google_ads_device_targeting_set; for the raw ad-schedule criteria (hour-of-day targeting config, NOT performance segmentation by hour) use google_ads_schedule_targeting_list.

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?

No annotations provided, so description carries full burden. It states the tool is read-only, describes edge cases (empty devices list when no data, cpa=None when conversions==0), and details insight triggers (high spend with zero conversions, CPA ratio >1.5x, low mobile CTR). This fully discloses behavior.

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?

The description is front-loaded with purpose and packed with essential details. Each sentence adds value, including output structure, edge cases, and sibling differentiation. Despite length, it is efficient and well-organized.

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 thoroughly explains the return format, including field details (ctr percent, cpa None condition), sorting, and insight triggers. It covers all aspects for an agent to understand behavior and results without additional documentation.

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%, but description adds significant value: explains customer_id fallback behavior, directs how to obtain campaign_id (via google_ads_campaigns_list), and provides usage recommendations for the period enum values (e.g., use shorter windows for recent changes).

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 compares campaign performance across device segments (Desktop/Mobile/Tablet) and specifies the output structure. It also distinguishes from sibling tools like google_ads_bid_adjustments_update and google_ads_device_targeting_set, making its unique purpose unambiguous.

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 (comparing device performance) and when to use alternatives (bid adjustments via google_ads_bid_adjustments_update, schedule targeting via google_ads_schedule_targeting_list). It also advises on the period parameter for different diagnostic 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