Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ads_ad_group_performance

Read-only

Retrieve ad group performance metrics for a specified date range, optionally filtered by campaign, to analyze Google Ads results.

Instructions

Ad group performance for a date range, optionally within one campaign.

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": {
      "customerId": "<customerId>"
    },
    "name": "ads_ad_group_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
endDateNo
dateRangeNoLAST_30_DAYS
startDateNoYYYY-MM-DD; overrides dateRange when used with endDate
campaignIdNo
customerIdYesGoogle Ads customer ID (with or without dashes)
loginCustomerIdNoManager (MCC) ID if accessing through a manager; defaults to ads.json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds nothing further: no mention of which metrics are returned, how pagination behaves via limit, whether results are aggregated by ad group, or what auth context (MCC via loginCustomerId) is needed.

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?

A single front-loaded sentence with no filler, and the core scoping information comes first. It is efficient, though the terseness leaves several parameters and behaviors unexplained.

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 7 parameters, under-half schema coverage, no output schema, and no annotations telling the agent what data comes back, the description should say what the report contains (metrics, row granularity, limit behavior). None of that is present, leaving the definition inadequate for a reporting 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 43%, so the description must compensate for undocumented parameters such as limit, endDate, dateRange's enum semantics, and campaignId. It only gestures at 'date range' and 'one campaign' and does not clarify the precedence between dateRange and startDate/endDate that the schema itself mentions.

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?

States a specific resource ('ad group performance') and its two scoping axes: a date range and an optional single campaign. The 'ad group' granularity distinguishes it from ads_campaign_performance and ads_ad_performance at a conceptual level, though the description never explicitly contrasts them.

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?

The phrase 'optionally within one campaign' hints that campaignId narrows scope, but there is no guidance on when to pick this tool over ads_ad_performance or ads_campaign_performance, no prerequisites, and no note about which reporting level an agent should prefer.

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