Skip to main content
Glama
Sign In
Google Analytics 4 MCP Server

Google Analytics 4 MCP Server

by stucchi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_key_event

Marks a specified event as a key event (conversion) in a Google Analytics 4 property.

Instructions

Mark an event as a key event (conversion).

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_id": "<property_id>",
      "event_name": "<event_name>"
    },
    "name": "create_key_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_nameYes
property_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral transparency. It does not disclose whether the operation is idempotent, whether it overwrites existing key event status, or what happens if the event is already a key event. This is insufficient.

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

Conciseness2/5

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

The description is very short (one sentence, 7 words), but it under-specifies the tool. Conciseness is valued, but not at the cost of omitting essential information.

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?

Given the tool has 2 parameters, an output schema, and a clear domain (Google Analytics key events), the description should at least explain the purpose of the parameters and the result. It fails to do so, leaving the agent to guess critical details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, and the tool description does not explain what the two required parameters (event_name, property_id) represent, what formats they expect, or how they relate to the operation. The description adds no value beyond the schema's structural types.

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 clearly states the action ('mark an event as a key event') and the resource ('event'), with parenthetical clarification ('conversion'). It distinguishes from sibling tools like delete_key_event and list_key_events, but could be more explicit about what a key event is.

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 description provides no guidance on when to use this tool versus alternatives (e.g., when creating versus listing or deleting key events). No prerequisites, contexts, or exclusions are mentioned.

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