grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.properties.conversionEvents.get

Retrieve a single Google Analytics conversion event by its resource name and return the resource as JSON. Deprecated: use GetKeyEvent instead.

Instructions

Deprecated: Use GetKeyEvent instead. Retrieve a single conversion event [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: create, delete, list, patch.

Input Schema

Name	Required	Description
`name`	Yes	[URL path segment] Required. The resource name of the conversion event to retrieve. Format: properties/{property}/conversionEvents/{conversion_event} Example: "properties/123/conv
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.

Output Schema

Name	Required	Description	Default
`name`	No
`custom`	No
`deletable`	No
`eventName`	No
`createTime`	No
`countingMethod`	No
`defaultConversionValue`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / name / description

Previous value: -"Required. The resource name of the conversion event to retrieve. Format: properties/{property}/conversionEvents/{conversion_event} Example: \"properties/123/conv"New value: +"[URL path segment] Required. The resource name of the conversion event to retrieve. Format: properties/{property}/conversionEvents/{conversion_event} Example: \"properties/123/conv"

addedInput schema / properties / name / pattern

Added value: +"^properties/[^/]+/conversionEvents/[^/]+$"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "countingMethod": {
+      "enum": [
+        "CONVERSION_COUNTING_METHOD_UNSPECIFIED",
+        "ONCE_PER_EVENT",
+        "ONCE_PER_SESSION"
+      ],
+      "type": "string"
+    },
+    "createTime": {
+      "type": "string"
+    },
+    "custom": {
+      "type": "boolean"
+    },
+    "defaultConversionValue": {
+      "properties": {
+        "currencyCode": {
+          "type": "string"
+        },
+        "value": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "deletable": {
+      "type": "boolean"
+    },
+    "eventName": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that this is an HTTP GET returning the resource as JSON, which signals a read-only operation, plus the deprecation status. It says nothing about authorization/scopes, error behavior for a missing or malformed resource name, or idempotency, and the body-building/body_file prose is irrelevant for a GET and adds noise rather than insight.

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?

Deprecation and purpose are correctly front-loaded, but the second sentence lards in request-body construction and body_file precedence that are meaningless for a GET retrieval, so not every sentence earns its place.

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?

An output schema exists, so return-value detail is not required, and all five parameters are fully documented in the schema, leaving deprecation and read-only nature as the main things the description must convey — which it does. Missing auth/permission context keeps it short of a 5.

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%, including the resource-name pattern and format example, so the schema already does the heavy lifting and baseline 3 applies. The description's mention that typed parameters win over the params map and that body_file can supply the body largely restates what the schema fields already say.

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 ("Retrieve a single conversion event") and explicitly enumerates the sibling operations over the same resource (create, delete, list, patch), so an agent can distinguish it from those siblings without inspecting schemas. The deprecation pointer to GetKeyEvent is front-loaded.

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?

It gives a clear routing instruction — deprecated, use GetKeyEvent instead — and lists the sibling operations to contrast against, implying use list to enumerate and patch/delete to mutate. It does not spell out explicit when-not conditions beyond the deprecation notice.

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

Deploy Server