Skip to main content
Glama
flin-ga4-mcp

flin-ga4-mcp

by flin-agency

search_change_history

Read-onlyIdempotent

Read Google Analytics 4 configuration change history, filtering by account, property, time, action, actor, and resource type to diagnose recent settings changes.

Instructions

Read configuration change history, requiring appropriate Editor/Administrator access.

ga_account_id is numeric or accounts/123 from list_properties; account is a login alias. property_id optionally limits the search; omission searches the account, ignoring the default property. Times are RFC3339, e.g. 2026-10-01T00:00:00Z. actions: CREATED/UPDATED/DELETED. resource_types uses Google's ChangeHistoryResourceType enum; actor_emails filters editors. Follow nextPageToken with identical filters even after an empty page. Secret values are redacted. Changes offer diagnostic context, not proof of the cause of traffic changes.

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": {
      "ga_account_id": "<ga_account_id>"
    },
    "name": "search_change_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
actionsNo
page_sizeNo
page_tokenNo
property_idNo
actor_emailsNo
ga_account_idYes
resource_typesNo
latest_change_timeNo
earliest_change_timeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: Editor/Administrator access requirement, secret-value redaction, the empty-page pagination trap, and an interpretive caveat that changes are not proof of traffic-change causes. These are exactly the behavioral details annotations cannot carry.

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?

Front-loaded with purpose and access requirement, then dense per-parameter sentences with no filler. The telegraphic style is efficient though slightly clipped, and the pagination note could be folded into the page_token discussion rather than sitting standalone.

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?

For a 10-parameter read tool with an output schema and full annotation coverage, the description supplies everything needed to invoke it correctly except page_size limits and the page_token/nextPageToken correspondence. Auth, filtering, time format, and pagination edge cases are all addressed.

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 description coverage is 0%, so the description must compensate, and it largely does: ga_account_id formats (numeric or accounts/123 from list_properties), account as login alias, property_id omission semantics, RFC3339 time format with example, and valid actions/resource_types vocabularies. page_size and the mapping between page_token and nextPageToken are left undocumented, leaving a small gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource combination — reading GA4 configuration change history — with the access prerequisite stated up front. No sibling tool (get_property_configuration, run_report, list_property_annotations) overlaps with this scope, so an agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives concrete scoping rules (omitting property_id searches the account and ignores the default property), filter semantics for actions/resource_types/actor_emails, and pagination guidance to follow nextPageToken with identical filters even after an empty page. It also warns the results are diagnostic context rather than causal proof. It never names an alternative tool or an explicit when-not-to-use, which keeps it below a 5.

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