Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

analyticsadmin.properties.firebaseLinks.create

Creates a FirebaseLink to connect a Firebase project to a Google Analytics property, returning JSON; supports dry-run preview and is blocked in read-only profiles.

Instructions

Creates a FirebaseLink. Properties can have at most one FirebaseLink [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 GoogleAnalyticsAdminV1betaFirebaseLink object accepting createTime, name, project; pass it via params or whole via body_file Siblings over the same resource: delete, list.

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. Format: properties/{property_id} Example: `properties/1234`
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. The body is a JSON GoogleAnalyticsAdminV1betaFirebaseLink object.
request_bodyNoRequest body of type GoogleAnalyticsAdminV1betaFirebaseLink: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

NameRequiredDescriptionDefault
nameNo
projectNo
createTimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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 GoogleAnalyticsAdminV1betaFirebaseLink object."
    • addedInput schema / properties / request_body
      Added value: +{
+  "description": "Request body of type GoogleAnalyticsAdminV1betaFirebaseLink: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "createTime": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "project": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / parent / description
      Previous value: -"Required. Format: properties/{property_id} Example: `properties/1234`"New value: +"[URL path segment] Required. Format: properties/{property_id} Example: `properties/1234`"
    • addedInput schema / properties / parent / pattern
      Added value: +"^properties/[^/]+$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "createTime": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "project": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description does substantial work: it declares the HTTP method (POST), flags that this creates or triggers a change, and uniquely discloses that the call is refused under --readonly safety profiles. It also states the return shape. It stops short of permission/scope requirements or error semantics, which is the remaining gap for an unannotated mutation tool.

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 verb+resource is front-loaded and the whole definition is a single compact passage with no filler. It is dense and dash-chained, and the body_file/params restatement slightly duplicates the schema, but nothing is wasted.

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 the return-value explanation is optional and correctly kept brief. For a create tool with a nested body object and six parameters, the description covers the precondition, the safety gate, the body shape, and the alternatives — only permission requirements are absent.

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 coverage is 100%, so baseline would be 3, but the description adds the meaningful detail that the body is a GoogleAnalyticsAdminV1betaFirebaseLink accepting createTime, name, and project, and that it can be supplied either via `params` (merged) or wholesale via `body_file`. That clarifies the two-path body construction beyond what the schema fields state in isolation.

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 opens with a specific verb+resource ("Creates a FirebaseLink") and immediately scopes it against the sibling operations on the same resource (delete, list). An agent can distinguish this from firebaseLinks.delete and firebaseLinks.list without opening either schema.

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 supplies a real precondition — "Properties can have at most one FirebaseLink" — which tells the agent to check existing state before calling, and it names the sibling alternatives delete and list. It does not explicitly say "use list first to verify no link exists," so the routing is implied rather than spelled out.

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