Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ads_campaign_performance

Read-only

Retrieves Google Ads campaign metrics for a date range, including impressions, clicks, cost, conversions, and ROAS, to analyze performance and inform budget decisions.

Instructions

Campaign performance for a date range: status, type, daily budget, impressions, clicks, CTR, avg CPC, cost, conversions, conversion value, cost/conversion and ROAS.

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_campaign_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
endDateNo
dateRangeNoLAST_30_DAYS
startDateNoYYYY-MM-DD; overrides dateRange when used with endDate
customerIdYesGoogle Ads customer ID (with or without dashes)
includePausedNo
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

B3/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 value by enumerating the returned metrics (CTR, avg CPC, cost, ROAS, etc.), which partly substitutes for the missing output schema, but says nothing about pagination (limit defaults to 200), the includePaused default of true, or authentication requirements.

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?

It is a single front-loaded sentence with the resource and scope first and the metric list after; nothing is padded. The metric enumeration is long but earns its place as the only statement of what the tool returns.

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?

For a read-only reporting tool with no output schema, the metric list makes the return content reasonably complete. However, with 7 parameters at 43% description coverage and no annotations covering defaults, the definition leaves the agent guessing about pausing filters, row limits, and manager-account access.

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% across 7 parameters, so the description should compensate, but apart from echoing 'date range' it explains none of them: limit, includePaused, and loginCustomerId are undocumented in both places, and startDate/endDate formatting is left entirely to the schema.

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 a specific resource and scope: 'Campaign performance for a date range', followed by an explicit list of the metrics returned. The word 'campaign' distinguishes it from sibling report tools such as ads_ad_group_performance and ads_ad_performance, although the description never states that contrast itself.

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 when-to-use guidance is given: nothing says when to choose campaign-level performance over ad-group, ad, or keyword performance, and no prerequisites are named (for example, that customerId is required or that an MCC loginCustomerId applies). The 'for a date range' phrase only weakly implies the reporting use case.

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