Skip to main content
Glama

MetricPort

Performance Max asset groups

ads_pmax_asset_groups
Read-onlyIdempotent

Asset groups of Performance Max campaigns with ad strength, cost, conversions and value. The only per-group visibility PMax offers.

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": {
      "property": "<property>"
    },
    "name": "ads_pmax_asset_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateNo
propertyYesGoogle Ads customer id from list_properties, e.g. 1234567890
startDateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, non-destructive, and openWorld, so safety is covered. The description adds that this is the only per-group visibility PMax offers, a useful behavioral constraint, but says nothing about date-range behavior, default ranges, or required property context.

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?

Two short sentences, front-loaded with the resource and metrics, with no filler. It is efficient, though slightly terse on context.

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?

With no output schema, low schema coverage, and no annotations about behavior beyond safety, the description should explain date-range handling and the required customer ID property, and possibly the return shape. It leaves too much implicit for a 3-parameter analytics query tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%; only the property parameter has a schema description, and startDate/endDate have patterns but no semantic description. The tool description adds no parameter guidance (e.g., date range defaults or required property), so the gap is not compensated.

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?

Names the specific resource (asset groups) and lists the metrics returned (ad strength, cost, conversions, value), plus the scope (Performance Max campaigns). It doesn't explicitly differentiate from siblings like ads_campaign_performance, but the resource is distinct enough to be identifiable.

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 statement of when to use this tool versus alternatives such as ads_campaign_performance or ads_query, and no prerequisites or exclusions are given. The 'only per-group visibility PMax offers' line hints at uniqueness but is not framed as usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.