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

flin-google-ads-mcp

by flin-agency

get_change_events

Read-only

Retrieve recent Google Ads account change events to audit adjustments and troubleshoot account changes, with filters for date range, resource type, and customer ID.

Instructions

Get recent Google Ads account change events from the change_event resource.

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_change_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
end_dateNo
start_dateNo
user_emailNo
customer_idNo
resource_typeNo
login_customer_idNo

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 declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no pagination behavior, no explanation of how 'recent' interacts with limit/start_date/end_date defaults, and no authentication or account-scoping notes. It does not contradict the annotations.

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

Conciseness3/5

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

It is a single front-loaded sentence with no filler, which is structurally clean. However, the brevity is under-specification rather than efficiency, since nothing substantive follows the verb and resource.

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

Completeness3/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 described, and the annotations cover safety. But for a 7-parameter tool with zero schema coverage, the definition leaves the agent without enough information to set account-scoping or date filters correctly.

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 7 parameters, so the description must carry the burden and it does not. It never explains customer_id vs login_customer_id, what user_email or resource_type filter, or the units/format of start_date and end_date; only 'recent' loosely gestures at the date parameters.

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 uses a specific verb plus resource ('Get ... change events') and even names the underlying 'change_event resource', so an agent knows exactly what data is returned. It does not differentiate itself from siblings like get_insights or get_campaigns, which is why 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 Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives for retrieving account activity. The word 'recent' implies a default recency window but never defines it or explains when a different tool is more appropriate.

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