Skip to main content
Glama

Visibility Genies

Read Google Ads campaigns

get_google_ads_campaigns
Read-only

The connected Google Ads account's campaigns for a period, from what the daily pull stored: impressions, clicks, click through rate, average cost per click, cost, conversions, conversion rate, cost per conversion and conversion value, most spend first, with each campaign's details as Google has them now (type, status, bid strategy and daily budget). Campaign numbers reach back 13 months. With withImpressionShare it also asks Google for each Search campaign's impression share and the share lost to budget and to rank (impressionShare says whether Google answered); nothing else here calls Google. Money is in the account's currency (currencyCode). Read-only; uses no credits.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_google_ads_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNoA named period ending on the last stored day (default last_3_months). Ignored when startDate and endDate are given.
endDateNoLast day (YYYY-MM-DD). Use with startDate; at most 730 days.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoFirst day (YYYY-MM-DD, the Ads account's time zone).
withImpressionShareNoAlso give each Search campaign's impression share and the share lost to budget and to rank. These are the only numbers asked of Google when the tool runs (held for 10 minutes); every other number is stored. Default false.

Output Schema

NameRequiredDescriptionDefault
okYes
metaNo
rowsNo
reasonNo
endDateNo
hasMoreNo
messageNo
failedAtNo
rowCountNo
startDateNo
connectUrlNo
storedFromNo
accountNameNo
currencyCodeNo
storedThroughNo
numbersStartOnNo
impressionShareNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, but the description adds substantive behavior beyond them: numbers come from a stored daily pull, history reaches back 13 months, only the impression-share path calls Google and results are held 10 minutes, money is in the account's currencyCode, and the call consumes no credits. The only gap is the shape/size of the returned set, which the output schema covers.

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?

The definition is front-loaded with the resource and its source of truth before the metric enumeration, and each clause carries non-redundant information (history depth, currency, credit cost, live-call behavior). The long comma-chained metric list is dense but is the tool's actual payload, so little is wasted; minor tightening of the metric run-on would improve it.

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

Completeness5/5

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

Given a stored-data read with an output schema, a fully documented 5-parameter schema, and annotations covering the safety profile, the description supplies everything an agent still needs: data freshness/source, 13-month limit, currency, credit cost, and the one condition under which an external Google call happens. Nothing material for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning: the range default and that explicit dates override it, and notably that withImpressionShare is the sole live-Google path with a 10-minute hold and that impressionShare signals whether Google answered. These are semantics an agent would not get from the schema alone.

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 opens with a specific verb+resource+scope: the connected Google Ads account's campaigns for a period, sourced from the daily pull, listing exactly which metrics and campaign attributes come back. An agent can tell this is the campaign-level performance read rather than a breakdown, term, or landing-page report. It stops short of naming a sibling tool to contrast with, so it lands at 4 rather than 5.

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?

Usage context is implied rather than stated: 'Campaign numbers reach back 13 months' and 'With withImpressionShare it also asks Google...' tell the agent when the flag matters and when the data is historical. There is no explicit when-to-use/when-not guidance relative to the many sibling Google Ads tools (breakdowns, search terms, conversion actions), so the agent must infer selection from the metric list.

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.

Resources