Google Ads MCP Server

get_campaign_performance

Retrieve performance metrics for Google Ads campaigns by customer ID, with options to filter by date range and campaign. Get key data to analyze campaign effectiveness.

Instructions

Get campaign performance metrics

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "customerId": "<customerId>"
    },
    "name": "get_campaign_performance"
  }
}

Input Schema

Name	Required	Description
`dateRange`	No	Date range (e.g., LAST_30_DAYS, LAST_7_DAYS)
`campaignId`	No	Optional campaign ID
`customerId`	Yes	Google Ads customer ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that performance metrics are retrieved, but does not explain what metrics are included, whether data is aggregated, pagination behavior, or any limitations. This is a significant gap for a reporting tool.

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

Conciseness2/5

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

The description is a single sentence that essentially restates the tool name, providing minimal informative value. It is not effectively concise; it is under-specified and does not earn its place by adding new information beyond the name.

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

Completeness2/5

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

The tool has no output schema, no annotations, and a brief description. It fails to explain what 'performance metrics' means (e.g., impressions, clicks, conversions), what date ranges are supported, or how to interpret results. This is incomplete for a tool that returns sophisticated data.

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?

The input schema provides descriptions for all three parameters (100% coverage), so the schema supplies the necessary meaning. The description adds no parameter detail itself, but the baseline of 3 is appropriate since the schema does the heavy lifting.

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?

The description clearly states the tool retrieves campaign performance metrics, using a specific verb ('get') and resource ('campaign performance metrics'). It is distinguishable from sibling tools like get_campaigns (which lists campaigns) and get_asset_performance (which focuses on assets), though it does not explicitly differentiate itself.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, filters, or scenarios where other tools might be more appropriate. Users are left to infer usage solely from the name and parameters.

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

Deploy Server