ads.report.pmax_asset_groupsRetrieves Performance Max asset-group performance data for a specified Google Ads customer and date range, so you can analyze which asset groups drive results.
Performance Max asset-group report.
| Name | Required | Description | Default |
|---|---|---|---|
| date_range | No | LAST_14_DAYS | |
| customer_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It implies a read-only reporting operation but says nothing about permissions, rate limits, pagination, or result shape beyond the existence of an output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The single sentence is front-loaded and free of waste, but it is under-specified rather than efficiently concise. It leaves obvious questions unanswered for a report tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, which reduces the need to describe return values. However, with no annotations and no parameter documentation, the definition is too sparse for an agent to call this report confidently without inspecting the schema manually.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so neither customer_id nor date_range is documented anywhere. The description adds no meaning about customer ID format or accepted date-range values beyond the schema default of LAST_14_DAYS.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific resource (Performance Max asset groups) and frames it as a report, which distinguishes it from sibling reports like ads.report.campaign or ads.report.search_terms. It is clear but does not explicitly state the granularity or metrics returned.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to choose this report versus ads.report.campaign, ads.report.ai_max, or ads.gaql.query. The agent must infer usage from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.