Skip to main content
Glama

Conversion tracking

conversion_tracking
Read-only

Audit Google Ads conversion tracking to see how conversions are counted, list all conversion actions with recent activity, and flag missing primary actions.

Instructions

How the account counts conversions: every conversion action (primary or secondary, type, source, counting, value, lookback, attribution, GA4 event) with its conversions in the window and last conversion date, the account's auto-tagging and conversion settings, the goals bidding uses, and a watch list (no primary action, primary actions that recorded nothing).

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": {
      "customer_id": "<customer_id>"
    },
    "name": "conversion_tracking"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, ending yesterday
customer_idYesGoogle Ads customer ID, with or without dashes (from list_accounts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.46.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. Beyond that the description adds genuine behavioral value by disclosing that the payload includes a 'watch' list flagging no-primary-action and primary-actions-with-zero-conversions, which tells the agent the output surfaces anomalies, not just raw data. It does not mention response size, limits, or whether watch items are deprioritized, keeping it from a 5.

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 dense sentence, but the scope is front-loaded ('How the account counts conversions') and the parenthetical enumerations each carry distinct information. Slightly run-on and list-heavy, though no sentence is filler.

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?

There is no output schema, so the description must carry the return-shape burden, and it does: it enumerates every returned section (per-action settings, counts in the window, last conversion date, account settings, bidding goals, watch list). Combined with complete schema parameter documentation and read-only annotations, nothing an agent needs to call it correctly 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% for both parameters, and the schema already documents the days look-back window and the customer_id format including its provenance from list_accounts. The description's 'in the window' phrase merely reinforces the schema rather than adding meaning. Baseline 3 is correct.

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 precisely and enumerates its scope: conversion actions (primary/secondary, type, source, counting, value, lookback, attribution, GA4 event), per-action conversion counts and last conversion date, account auto-tagging and conversion settings, bidding goals, and a watch list. An agent knows exactly what domain this covers. It does not, however, name or contrast a sibling (e.g. account_overview or run_gaql), so it falls short of a 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?

Use is implied by the enumerated scope — an agent can infer this is the conversion-measurement diagnostic view — but there is no explicit 'use this when' statement, no exclusions, and no pointer to alternatives such as account_overview for general settings or run_gaql for ad-hoc queries. Minimum viable routing guidance only.

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