Google Ads - AdLoop

Overview Schema Source Related Servers Discussions Admin

Campaign performance

get_campaign_performance

Read-only

Retrieves campaign performance metrics (impressions, clicks, cost, conversions, CPA, ROAS, CTR) for a date range, defaulting to last 30 days, with an optional compact summary for large accounts.

Instructions

Get campaign-level performance metrics for a date range.

Returns: campaign name, status, type, impressions, clicks, cost, conversions, CPA, ROAS, CTR for each campaign. Date format: "YYYY-MM-DD". Empty = last 30 days.

Set compact=true for audits/overviews on large accounts: returns account totals, status/type breakdowns, the top-10 spenders, and zero-conversion offenders instead of every row (~90% smaller).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`compact`	No
`customer_id`	No
`date_range_end`	No
`date_range_start`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.13.2Sep 7, 2026
Removedv0.13.0Jul 22, 2026
Changed1 schema field changedv0.12.0Jul 12, 2026
- addedInput schema / properties / compact
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
First observedv0.9.0Jun 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark readOnlyHint=true and destructiveHint=false. The description uses 'Get' and describes returns without any destructive or side-effect language, showing full consistency. It adds context about the compact mode, which is a behavioral variant, but not a side effect.

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, about 60 words, with a clear structure: purpose, returned fields, then usage notes on dates and compact mode. No fluff or repetition.

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?

Lists all key returned fields, provides date defaults, and explains the compact alternative. With an output schema present but not shown, the description covers the essential context for an agent to invoke the tool correctly.

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?

The schema has 4 parameters with 0% description coverage. The tool description covers date_range_start and date_range_end (format and default), and compact (behavior). However, customer_id is not mentioned at all. Given that 3 of 4 parameters are explained, it compensates well but not fully.

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 retrieves campaign-level performance metrics, lists the specific metrics returned, and implicitly distinguishes it from sibling tools like get_ad_performance or get_keyword_performance by focusing solely on campaigns.

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 explains date format (YYYY-MM-DD, empty = last 30 days) and provides guidance on when to use compact=true for large accounts, including what it returns. This gives clear operational instructions.

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

Deploy Server