Skip to main content
Glama

google_ads_ad_performance_report

Retrieve per-ad performance metrics from Google Ads, including impressions, clicks, cost, conversions, and CTR. Filter by ad group or campaign ID to analyze individual ad results across specified time periods.

Instructions

Report per-ad performance across Google Ads ad_group_ad rows. Returns one row per ad shaped as {ad_id, ad_type, status ('ENABLED'|'PAUSED'|'REMOVED'), ad_group_id, ad_group_name, campaign_id, campaign_name, metrics} where metrics contains impressions, clicks, cost_micros, cost (currency), conversions, ctr, average_cpc_micros, average_cpc, cost_per_conversion_micros, cost_per_conversion. Filterable by ad_group_id and/or campaign_id (both optional, both numeric). Read-only; no mutation. For ENABLED-only A/B comparison within a single ad group with WINNER/LOSER verdicts use google_ads_ad_performance_compare; for campaign-level aggregates use google_ads_performance_report.

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.
ad_group_idNoOptional ad group ID as a numeric string (e.g. '145680123456') to restrict results to a single ad group. Omit to include every ad group matching the campaign filter.
campaign_idNoOptional campaign ID as a numeric string (e.g. '23743184133') to restrict the report to a single campaign. Omit to aggregate across every campaign in the account.
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.
Behavior4/5

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

Description states 'Read-only; no mutation' and details the output shape including metric fields. Although annotations are absent, the description provides sufficient behavioral context (read-only, output structure, optional parameters with fallback).

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 a single well-structured paragraph with front-loaded purpose, followed by output shape, parameter details, read-only nature, and sibling differentiation. No unnecessary words.

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 the return shape, lists key metrics, covers all parameters with their roles, and provides filtering and period advice. It also clearly states read-only behavior and sibling alternatives.

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?

All four parameters are described in the schema (100% coverage). The description adds extra usage advice: 'Omit to include every ad group' for ad_group_id, and period descriptions like 'use a shorter window when diagnosing recent changes'. This adds value 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 'Report per-ad performance across Google Ads ad_group_ad rows' with a specific verb and resource. It distinguishes itself from sibling tools by naming alternatives for A/B comparison and campaign-level aggregates.

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?

Explicitly mentions when to use this tool (per-ad reporting) and when to use alternatives: google_ads_ad_performance_compare for A/B comparison within an ad group, and google_ads_performance_report for campaign-level aggregates. Also explains filtering options.

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