Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

analyticsadmin.properties.get

Fetches a single Google Analytics property by its resource name and returns the details as JSON for inspection or configuration checks.

Instructions

Lookup for a single GA Property [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: acknowledgeUserDataCollection, create, delete, getDataRetentionSettings, list, patch, runAccessReport, updateDataRetentionSettings.

Input Schema

NameRequiredDescriptionDefault
nameYes[URL path segment] Required. The name of the property to lookup. Format: properties/{property_id} Example: "properties/1000"
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.

Output Schema

NameRequiredDescriptionDefault
nameNo
parentNo
accountNo
timeZoneNo
createTimeNo
deleteTimeNo
expireTimeNo
updateTimeNo
displayNameNo
currencyCodeNo
propertyTypeNo
serviceLevelNo
industryCategoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Required. The name of the property to lookup. Format: properties/{property_id} Example: \"properties/1000\""New value: +"[URL path segment] Required. The name of the property to lookup. Format: properties/{property_id} Example: \"properties/1000\""
    • addedInput schema / properties / name / pattern
      Added value: +"^properties/[^/]+$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "account": {
+      "type": "string"
+    },
+    "createTime": {
+      "type": "string"
+    },
+    "currencyCode": {
+      "type": "string"
+    },
+    "deleteTime": {
+      "type": "string"
+    },
+    "displayName": {
+      "type": "string"
+    },
+    "expireTime": {
+      "type": "string"
+    },
+    "industryCategory": {
+      "enum": [
+        "INDUSTRY_CATEGORY_UNSPECIFIED",
+        "AUTOMOTIVE",
+        "BUSINESS_AND_INDUSTRIAL_MARKETS",
+        "FINANCE",
+        "HEALTHCARE",
+        "TECHNOLOGY",
+        "TRAVEL",
+        "OTHER",
+        "ARTS_AND_ENTERTAINMENT",
+        "BEAUTY_AND_FITNESS",
+        "BOOKS_AND_LITERATURE",
+        "FOOD_AND_DRINK",
+        "GAMES",
+        "HOBBIES_AND_LEISURE",
+        "HOME_AND_GARDEN",
+        "INTERNET_AND_TELECOM",
+        "LAW_AND_GOVERNMENT",
+        "NEWS",
+        "ONLINE_COMMUNITIES",
+        "PEOPLE_AND_SOCIETY",
+        "PETS_AND_ANIMALS",
+        "REAL_ESTATE",
+        "REFERENCE",
+        "SCIENCE",
+        "SPORTS",
+        "JOBS_AND_EDUCATION",
+        "SHOPPING"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "parent": {
+      "type": "string"
+    },
+    "propertyType": {
+      "enum": [
+        "PROPERTY_TYPE_UNSPECIFIED",
+        "PROPERTY_TYPE_ORDINARY",
+        "PROPERTY_TYPE_SUBPROPERTY",
+        "PROPERTY_TYPE_ROLLUP"
+      ],
+      "type": "string"
+    },
+    "serviceLevel": {
+      "enum": [
+        "SERVICE_LEVEL_UNSPECIFIED",
+        "GOOGLE_ANALYTICS_STANDARD",
+        "GOOGLE_ANALYTICS_360"
+      ],
+      "type": "string"
+    },
+    "timeZone": {
+      "type": "string"
+    },
+    "updateTime": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses the HTTP verb (GET), that it returns the resource as JSON, and how the request is constructed (typed params win over the `params` map, or body read from `body_file`). It omits any auth/permission requirements, though 'Lookup' plus '[HTTP GET]' reasonably convey a read-only 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?

Purpose is front-loaded, but the trailing request-body construction note is boilerplate that is largely irrelevant to a GET, and the sibling-routing is a raw dump of eight names rather than useful differentiation. Some content earns its place; some does not.

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?

With an output schema present, return values need not be explained, and the description covers purpose and request construction adequately for a single-resource GET. Only auth/permission context is missing, which is a minor gap.

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 the schema already documents all 5 parameters, setting a baseline of 3. The description reinforces the precedence rule (typed params win over `params`, body from `body_file`) but adds little beyond what is already in the schema.

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?

States a specific verb and resource: 'Lookup for a single GA Property [HTTP GET]. Returns the requested resource as JSON.' This clearly distinguishes it as the single-resource read among the properties.* family. The sibling list is provided but not used for differentiation, so it falls short of a 5.

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?

The description enumerates siblings over the same resource (list, patch, delete, etc.), which implies this is the point-get, but it never states when to use this versus analyticsadmin.properties.list or patch. Routing is left to inference from the verb.

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