Skip to main content
Glama

google_ads_device_analyze

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

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
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.
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?

Despite no annotations, the description fully discloses behavior: read-only, returns empty devices list when no data, insights triggers for specific conditions, and cpa is None when conversions == 0.

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?

Concise yet comprehensive. Front-loaded purpose, structured return format, edge cases, and sibling references. Every sentence adds value without 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?

Given no output schema, the description fully explains return structure, edge cases, and related tools. Completeness is high for a 3-param, 1-required tool.

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 significant value: period usage guidance, customer_id fallback, campaign_id source. Enhances understanding beyond the schema.

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 purpose: 'Compare Google Ads campaign performance across device segments (Desktop / Mobile / Tablet).' It specifies the verb, resource, and scope, distinguishing it from siblings like google_ads_bid_adjustments_update.

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?

Explicit guidance is provided: when to use (device performance comparison), when not to (for bid adjustments, use google_ads_bid_adjustments_update), and hints for period selection (short window for diagnosing, long for trends).

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