Skip to main content
Glama

google_ads_performance_report

Aggregate campaign-level performance metrics for a Google Ads account over a specified reporting window. Returns impressions, clicks, cost, conversions, and derived metrics per campaign.

Instructions

Aggregate campaign-level performance metrics for a Google Ads account over a reporting window. Returns one row per campaign shaped as {campaign_id, campaign_name, metrics}, where the metrics object contains impressions, clicks, cost_micros, cost (currency-formatted), conversions, ctr, average_cpc_micros, average_cpc, cost_per_conversion_micros, and cost_per_conversion. Read-only; no mutation. Use this for campaign-level totals. For per-ad breakdowns use google_ads_ad_performance_report; for Google Search vs. Search Partners splits use google_ads_network_performance_report; for query-level detail use google_ads_search_terms_report; for conversion-action slicing use google_ads_conversions_performance.

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_idNoRestrict the report to a single campaign by numeric ID (e.g. '23743184133'). 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?

Declares read-only and no mutation, which is important given no annotations. Additionally, describes the return shape in detail. However, does not mention auth prerequisites, rate limits, or handling of invalid customer IDs, which are minor gaps.

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 concise, front-loaded with purpose and return shape, and efficiently lists sibling tools in a single sentence. Every sentence serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 details the return shape and the metrics fields. It covers optional parameters, default behavior, and sibling tools. Missing pagination info or response size limits, but sufficiently complete for a read-only report tool.

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?

Schema coverage is 100% so baseline is 3. The description adds value by providing usage context for the period parameter (e.g., using shorter windows for recent changes). No additional info for customer_id or campaign_id beyond 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 tool aggregates campaign-level performance metrics over a reporting window, specifying the return shape and distinguishing from sibling tools by naming alternatives for different granularities.

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 states when to use this tool (campaign-level totals) and provides alternatives for per-ad, network, search terms, and conversion reports. Also gives guidance on choosing the period parameter for different analysis 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