Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

ads_query

Read-only

Run read-only GAQL queries against a Google Ads account to retrieve campaign and metrics data, with _micros money fields returned in currency units.

Instructions

Run any read-only GAQL query against a Google Ads account (e.g. SELECT campaign.name, metrics.clicks FROM campaign WHERE segments.date DURING LAST_7_DAYS). Money fields ending in _micros are returned in currency units.

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>",
      "query": "<query>"
    },
    "name": "ads_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description is consistent with both ('read-only GAQL query'). It adds genuinely non-structured context in noting that money fields suffixed _micros are returned in currency units, which matters for interpreting results since there is no output schema. It does not mention row limits, pagination, or whether errors are returned per-query.

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

Conciseness5/5

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

Two sentences, front-loaded with the core capability, and the inline SELECT example plus the _micros note each carry distinct information. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-query read tool with annotations covering its safety profile, the description covers the essential call shape and one important return-value nuance. The remaining gap is the undocumented limit parameter and result-set behavior, which is a moderate omission given no output schema exists.

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

Parameters3/5

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

Schema description coverage is 50%: customerId and loginCustomerId are documented in the schema, while query and limit are not. The description compensates for query by showing GAQL syntax and semantics, but says nothing about limit (default 500, max 10000) or how loginCustomerId interacts with manager accounts, leaving a real gap.

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 verb and resource — run a read-only GAQL query against a Google Ads account — and backs it with a concrete query example, so the agent knows exactly what the tool does. It does not explicitly name the prebuilt performance siblings (ads_campaign_performance, etc.) as the alternative, so the differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Run any read-only GAQL query' implies this is the general-purpose escape hatch for cases the fixed report tools don't cover, but the description never says when to prefer it over the sibling report tools or when it is unnecessary. Usage context is implied only.

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