Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_key_events_list

List key events for a GA4 property, including event name, counting method, and deletability. Use it to review current conversion events without modifying the property.

Instructions

List key events (formerly "conversion events") for a GA4 property — the current Admin API naming. Returns event name, counting method, and whether the event is deletable. Read-only.

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": {
      "property": "<property>"
    },
    "name": "ga4_key_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxPagesNoMaximum number of API pages to fetch (default 50). If more pages remain, the result includes truncated:true and a nextPageToken.
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".
pageTokenNoContinuation token to resume listing from a previous truncated result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / maxPages / maximum
      Added value: +9007199254740991
    • removedInput schema / properties / property / minLength
      Removed value: -1
    • addedInput schema / properties / property / pattern
      Added value: +"^\\s*(properties\\/)?\\d+\\s*$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the disclosure burden and does so well on the critical axis by explicitly declaring "Read-only". It also previews the returned fields (event name, counting method, deletability), which orients the agent on data shape. It omits permission requirements and only alludes to pagination via the schema, keeping it just short of 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.

Conciseness5/5

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

Two short sentences, front-loaded with the action and resource, then the return shape. Every clause earns its place by resolving a real ambiguity (the legacy naming) and setting expectations about output and safety.

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 simple paginated read tool with full schema coverage and no output schema, the description covers purpose, safety, and a summary of returned fields. A slightly fuller sketch of the response shape or permission needs would make it airtight, but nothing essential is missing for correct invocation.

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 property pattern, pageToken semantics, and maxPages/truncated behavior all documented in the schema itself. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies.

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 and resource ("List key events ... for a GA4 property") and disambiguates the resource by noting the current Admin API naming versus the deprecated "conversion events" term. Combined with the sibling names (create/delete/update_key_event), an agent can immediately tell this is the read side of the key-event family.

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 implied rather than stated: it's evidently the tool to call when enumerating key events for a property, and the CRUD siblings make the alternative obvious. However, it never explicitly says when to prefer this over other listing tools or what prerequisite state (property must exist, permissions) is needed, so guidance remains inferential.

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

Deploy Server

Other Tools