Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ads_ad_performance

Read-only

Retrieve ad-level performance metrics, including responsive search ad headlines and descriptions, by customer, date range, or campaign.

Instructions

Ad-level performance including responsive search ad headlines/descriptions.

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_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.6/5.0
Behavior2/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the lower bar applies, but the description adds essentially nothing: it does not state default reporting window (LAST_30_DAYS), row limits, whether metrics are per-ad aggregates, or that an MCC login ID may be needed. Nothing here helps an agent predict the shape or cost of the call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single clause is front-loaded and free of padding, but it is concise to the point of under-specification for a 7-parameter reporting tool. Nothing is wasted, but very little is delivered.

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?

For a read-only analytics endpoint with no output schema, the description should say what metrics or fields come back and at what granularity; it only hints at RSA asset data. Combined with the low parameter coverage and missing usage guidance, an agent cannot confidently form a correct call or interpret results.

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 description coverage is only 43% across 7 parameters, so the description should compensate, yet it mentions none of them — not customerId, campaignId, dateRange, or the startDate/endDate override behavior. Only the schema-only descriptions (customerId, loginCustomerId, startDate) carry any meaning, leaving limit, campaignId, and endDate undocumented anywhere.

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 names the resource and granularity ('Ad-level performance') plus an extra data dimension (responsive search ad headlines/descriptions), which implicitly separates it from the campaign/ad_group/keyword performance siblings. It stops short of explicitly routing between those levels, so it is clear but not fully differentiated.

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?

There is no when-to-use guidance, no condition for choosing ad-level over campaign- or ad-group-level performance, and no mention of alternatives such as ads_query for custom reporting. The agent must infer all selection logic from the tool name alone.

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