Skip to main content
Glama

get_google_campaign_report

Fetch live Google Ads campaign performance metrics (impressions, clicks, cost, conversions, CTR, average CPC) via GAQL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_google_campaign_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateRangeNoReporting window (default: LAST_30_DAYS).
customerIdNo10-digit Google Ads customer ID (optional if set in your MCP token).
loginCustomerIdNoOptional 10-digit MCC login customer ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden; 'live' is a useful hint that data is fetched in real time rather than cached. It omits whether this is a read-only query, expected latency/cost of GAQL execution, rate limits, and whether results are per-campaign or aggregated — all material for a reporting call with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that packs the verb, resource, metric list and query mechanism with no filler. The metric enumeration is dense but earns its place by substituting for the absent output schema.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Listing the returned metrics partially compensates for the missing output schema, and the schema covers all three optional parameters. However, with no annotations and no output schema, the definition still leaves the result shape (one row per campaign?) and any auth/side-effect profile unstated.

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

Parameters3/5

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

Schema description coverage is 100%, so dateRange, customerId and loginCustomerId are already fully documented in the schema with defaults and formats. The description adds no parameter meaning beyond the passing mention of GAQL, which is baseline-adequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Fetch) and resource (Google Ads campaign performance metrics), then enumerates the exact metrics returned. It does not differentiate itself from siblings like list_google_ads_campaigns (account/campaign structure) or the mutation tools, but the reporting intent is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites, and no named alternatives. An agent must infer that this is the read-only reporting path versus list_google_ads_campaigns or whoami purely from the word 'performance metrics'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources