Skip to main content
Glama

Visibility Genies

Read Google Ads conversions

get_google_ads_conversion_actions
Read-only

The connected Google Ads account's conversions split by conversion action (purchase, sign-up, call and so on) for a period, from what the daily pull stored: conversions, conversion value and each action's share of all conversions, most conversions first. 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_conversion_actions"
  }
}

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).

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so safety is covered; the description adds genuinely new context by disclosing the data provenance ('from what the daily pull stored') — i.e. a snapshot rather than a live query — and a billing fact ('uses no credits'). The 'Read-only' clause duplicates readOnlyHint, but the provenance and credit cost are real additions beyond the structured fields.

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?

A single front-loaded sentence whose colon list efficiently enumerates the returned metrics, followed by a short billing/safety clause. No padding or redundancy beyond the minor overlap of 'Read-only' with the annotation.

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?

An output schema exists, so return shapes need not be described, and the description covers the metric set, ordering and data freshness. What remains thin is prerequisite context — it assumes the Ads account is already connected without saying so — but nothing critical for correct invocation is missing.

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 100%, with the named-period enum, the startDate/endDate pairing, the 730-day cap and the default already documented in the schema. The description only restates 'for a period' and does not add format or interaction nuances beyond what the schema provides, so the baseline 3 applies.

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 (Google Ads conversions), the split dimension (conversion action), the metrics returned (conversions, conversion value, share of all conversions) and the sort order (most conversions first). That level of detail lets an agent distinguish it from campaign- or term-level siblings, though no sibling is explicitly named for contrast.

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 is only implied: 'the connected Google Ads account's conversions split by conversion action' tells the agent what data this yields, but there is no explicit when-to-use framing and no pointer to an alternative (e.g. get_google_ads_campaigns) when campaign-level rather than action-level conversion data is wanted.

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