Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

analyticsadmin.properties.conversionEvents.list

Lists conversion events for a Google Analytics parent property, returning an empty list when none exist. Deprecated: use ListKeyEvents instead.

Instructions

Deprecated: Use ListKeyEvents instead. Returns a list of conversion events in the specified parent property. Returns an empty list if no conversion events are found [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, get, patch.

Input Schema

NameRequiredDescriptionDefault
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
parentYes[URL path segment] Required. The resource name of the parent property. Example: 'properties/123'
dry_runNoReturn the request that would be sent, without sending it.
pageSizeNo[query parameter] Optional. The maximum number of resources to return. If unspecified, at most 50 resources will be returned. The maximum value is 200; (higher values will be coe
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.
pageTokenNo[query parameter] Optional. A page token, received from a previous `ListConversionEvents` call. Provide this to retrieve the subsequent page. When paginating, all other parameter

Output Schema

NameRequiredDescriptionDefault
nextPageTokenNo
conversionEventsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / pageSize / description
      Previous value: -"Optional. The maximum number of resources to return. If unspecified, at most 50 resources will be returned. The maximum value is 200; (higher values will be coe"New value: +"[query parameter] Optional. The maximum number of resources to return. If unspecified, at most 50 resources will be returned. The maximum value is 200; (higher values will be coe"
    • addedInput schema / properties / pageSize / format
      Added value: +"int32"
    • changedInput schema / properties / pageToken / description
      Previous value: -"Optional. A page token, received from a previous `ListConversionEvents` call. Provide this to retrieve the subsequent page. When paginating, all other parameter"New value: +"[query parameter] Optional. A page token, received from a previous `ListConversionEvents` call. Provide this to retrieve the subsequent page. When paginating, all other parameter"
    • changedInput schema / properties / parent / description
      Previous value: -"Required. The resource name of the parent property. Example: 'properties/123'"New value: +"[URL path segment] Required. The resource name of the parent property. Example: 'properties/123'"
    • addedInput schema / properties / parent / pattern
      Added value: +"^properties/[^/]+$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "conversionEvents": {
+      "items": {
+        "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"
+      },
+      "type": "array"
+    },
+    "nextPageToken": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden: it discloses deprecation, that this is an HTTP GET (read-only), and that an empty list is returned when nothing matches. However, the generic 'request bodies are built from the typed parameters... or read whole from `body_file`' boilerplate describes body construction that a GET never performs, which is noise bordering on misleading for this operation.

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 in the first two sentences, but the trailing HTTP/body_file/params boilerplate is irrelevant to a read-only list call and dilutes the useful content. Trimming that sentence would improve the definition materially.

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 the required `parent` plus pagination parameters are fully covered by the schema. Combined with the deprecation notice and empty-list behavior, an agent has nearly everything needed; the only real gap is the unresolvable `ListKeyEvents` alternative name.

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%, so all seven parameters (parent, pageSize, pageToken, query, params, dry_run, body_file) are already documented in the schema; baseline 3 applies. The description adds no parameter-specific semantics — its only parameter-adjacent content (typed flags win over `params`) simply restates the schema's own `params` description.

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?

Specific verb+resource+scope: lists conversion events within a specified parent property, and explicitly names the four sibling operations on the same resource (create, delete, get, patch) so the agent can pick list without opening schemas. The deprecation notice front-loads the most decision-relevant fact.

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?

Says to use `ListKeyEvents` instead, which is a genuine when-to-use/alternative signal, but `ListKeyEvents` is not a resolvable tool name — the actual sibling is analyticsadmin.properties.keyEvents.list, so the agent must infer the mapping. No conditions or exclusions 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

Other Tools