Google Ads MCP Server

get_pmax_placement_performance

Read-only

Retrieve Performance Max campaign placement performance by channel—Search, YouTube, Display, Discover, and Gmail—for a specified date range so you can compare where ads deliver.

Instructions

Get PMax placement performance breakdown (Search, YouTube, Display, Discover, Gmail).

Args:
    customer_id: Google Ads customer ID.
    campaign_id: PMax campaign ID.
    date_range: Date range (predefined or 'YYYY-MM-DD,YYYY-MM-DD').

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>",
      "campaign_id": "<campaign_id>"
    },
    "name": "get_pmax_placement_performance"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 11, 2026

TDQS

A3.5/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 that results are broken out by placement channel (Search, YouTube, Display, Discover, Gmail), which is useful behavioral context, but says nothing about authentication, quotas, or metric availability.

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?

Front-loaded with the purpose in one sentence, followed by a compact Args block with no wasted prose. Slightly boilerplate in formatting but every line adds information.

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?

With no output schema, the description should clarify what is returned; it names the placement dimension but not the metrics (impressions, clicks, cost, conversions) or the response shape. For a read-only reporting tool this leaves a meaningful gap for the calling agent.

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 description coverage is 0%, so the description carries the burden, and it does: all three parameters are explained, including that campaign_id is specifically a PMax campaign and that date_range accepts a predefined value or 'YYYY-MM-DD,YYYY-MM-DD'. It stops short of listing the available predefined ranges.

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 states a specific verb ('Get') and resource ('PMax placement performance breakdown') and enumerates the placement channels returned. It is distinguishable from generic siblings like get_campaign_performance, though it never explicitly contrasts itself with them.

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?

Usage is only implied: an agent can infer this applies to a Performance Max campaign when placement-level data is needed. There is no explicit when-to-use vs. alternatives guidance or stated exclusions.

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

Deploy Server