Skip to main content
Glama
flin-google-ads-mcp

flin-google-ads-mcp

by flin-agency

get_conversion_insights

Read-only

Fetch conversion-only Google Ads metrics with optional date and conversion-action segmentation to analyze performance by campaign, ad group, or conversion action.

Instructions

Get conversion-only metrics with optional date and conversion-action segments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_conversion_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNocampaign
limitNo
end_dateNo
date_rangeNoLAST_30_DAYS
start_dateNo
ad_group_idNo
campaign_idNo
customer_idNo
segment_by_dateNo
login_customer_idNo
conversion_action_idNo
conversion_action_nameNo
segment_by_conversion_actionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. Beyond that the description adds almost nothing about behavior: it does not explain default date_range=LAST_30_DAYS behavior, that limit defaults to 100 (implying pagination/capping), or how segmentation changes the row grain of results.

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?

A single front-loaded sentence with no padding or redundancy. It is efficient, though the brevity reflects under-specification rather than disciplined editing; the core purpose is stated first.

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

Completeness2/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 values need not be explained, and annotations cover safety. However, for a 13-parameter, zero-coverage analytics tool with defaults and segmentation semantics, one sentence leaves the agent without enough to choose values confidently. It is not adequate for the tool's complexity.

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 description coverage is 0% across 13 parameters, so the description must carry the load. It only gestures at the date parameters and conversion-action segments, leaving level, limit, ad_group_id, campaign_id, customer_id, login_customer_id, and segment_by_date completely unexplained, and it never clarifies that level and the segment flags change aggregation.

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 gives a specific verb ('Get') and a scoped resource ('conversion-only metrics'), which implicitly separates it from the broader get_insights sibling. It stops short of naming the alternative tool or stating the scope boundary explicitly, but an agent can still tell what this tool returns.

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?

The phrase 'conversion-only' hints that this is the specialization for conversion metrics, but there is no explicit when-to-use, when-not-to-use, or named alternative such as get_insights. No prerequisites (customer_id, login_customer_id) or account-context requirements are mentioned.

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