google-ads-mcp

Overview Schema Source Related Servers Discussions Admin

get_campaign_performance

Read-only

Fetch Google Ads campaign performance metrics for a chosen date range, optionally filtered by campaign or status, to support reporting and optimization.

Instructions

Get campaign performance metrics over a date range.

Args: customer_id: Google Ads customer ID. date_range: Date range -- use predefined (LAST_7_DAYS, LAST_30_DAYS, THIS_MONTH, LAST_MONTH, etc.) or custom 'YYYY-MM-DD,YYYY-MM-DD'. campaign_id: Optional -- filter to a single campaign. status_filter: Optional -- filter by status (ENABLED, PAUSED, REMOVED). limit: Max rows to return (default 50).

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": {
      "customer_id": "<customer_id>"
    },
    "name": "get_campaign_performance"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`date_range`	No	LAST_30_DAYS
`campaign_id`	No
`customer_id`	Yes
`status_filter`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 4, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context like configurable date ranges and a row limit, but it does not disclose the return format, metric fields, aggregation, or any potential quirks for a metrics-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.

Conciseness5/5

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

The description is front-loaded with a clear one-sentence purpose, followed by a compact and structured Args list. Every line adds necessary semantic information that the schema does not provide, with no filler or repetition.

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?

All required parameters are explained in enough detail for a knowledgeable agent to invoke the tool. However, with no output schema, the description does not state which campaign performance metrics are returned or what the response rows look like, leaving a meaningful gap for interpreting results.

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 description coverage is 0%, so the description carries the full burden for parameter meaning. It documents all five parameters clearly, including predefined and custom date-range formats, acceptable status filter values, and the default limit.

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 opens with a specific verb and resource: 'Get campaign performance metrics over a date range.' This clearly identifies the operation and distinguishes it from sibling tools like get_campaign, get_ad_group_performance, or get_account_performance_summary.

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

Usage Guidelines3/5

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

The tool's intended use is implied by the name and description—campaign-level performance reporting—but there is no explicit guidance about when to choose it over alternatives such as get_campaign or get_keyword_performance. No exclusions or selection conditions are stated.

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

Deploy Server