grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.properties.create

Creates a Google Analytics property with specified location and attributes via HTTP POST, returning the API response as JSON; refused in read-only mode.

Instructions

Creates a Google Analytics property with the specified location and attributes [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON GoogleAnalyticsAdminV1betaProperty object accepting account, createTime, currencyCode, deleteTime, displayName, expireTime, industryCategory, name and 5 more fields; pass it via params or whole via body_file Siblings over the same resource: acknowledgeUserDataCollection, delete, get, getDataRetentionSettings, list, patch, runAccessReport, updateDataRetentionSettings.

Input Schema

Name	Required	Description
`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. The body is a JSON GoogleAnalyticsAdminV1betaProperty object.
`request_body`	No	Request body of type GoogleAnalyticsAdminV1betaProperty: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

Name	Required	Description	Default
`name`	No
`parent`	No
`account`	No
`timeZone`	No
`createTime`	No
`deleteTime`	No
`expireTime`	No
`updateTime`	No
`displayName`	No
`currencyCode`	No
`propertyType`	No
`serviceLevel`	No
`industryCategory`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / body_file / description

Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON GoogleAnalyticsAdminV1betaProperty object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type GoogleAnalyticsAdminV1betaProperty: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "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"
+}

Changed1 schema field changedOct 26, 2026

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"
+}

First observedOct 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the burden and discloses meaningful behavior: it is an HTTP POST that creates or triggers a change, is refused under readonly profiles, returns the API response as JSON, and accepts the request body via `params` or `body_file`. It does not describe required auth scopes or idempotency, but it provides substantially more behavioral context than a bare mutation description.

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

Conciseness4/5

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

The purpose is front-loaded and the description avoids filler. It is dense and packs multiple clauses plus a sibling list into one paragraph, which is informative but slightly harder to scan than a shorter multi-sentence structure.

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?

The tool is complex, but the description covers the mutation nature, return behavior, request body type, and input pathways. Since an output schema exists, it need not explain return values in detail; remaining gaps are mainly around permissions and precise when-to-use routing.

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

Parameters4/5

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

Schema description coverage is already 100%, so the baseline is 3. The description adds value by identifying the request body as a GoogleAnalyticsAdminV1betaProperty object, naming several accepted fields like account, createTime, currencyCode, displayName, and industryCategory, and clarifying that it can be passed via `params` or `body_file`.

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?

The description states a specific verb and resource: 'Creates a Google Analytics property with the specified location and attributes' and adds HTTP POST. It also names sibling operations over the same resource, so an agent can distinguish this creation tool from get, list, patch, delete, and related operations.

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?

Usage is clearly implied for creating a new property and the description explicitly notes it is 'refused under --readonly safety profiles,' which is useful invocation context. It lists sibling tools but does not explicitly say when to prefer create versus patch or update, so it lacks full alternative-selection guidance.

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

Deploy Server