grr

Overview Schema Source Related Servers Discussions Admin

analyticsadmin.properties.firebaseLinks.list

Lists Firebase links configured on an Analytics property, including pagination, to help you inspect which Firebase project is connected to that property.

Instructions

Lists FirebaseLinks on a property. Properties can have at most one FirebaseLink [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.

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.
`parent`	Yes	[URL path segment] Required. Format: properties/{property_id} Example: `properties/1234`
`dry_run`	No	Return the request that would be sent, without sending it.
`pageSize`	No	[query parameter] Optional. The maximum number of resources to return. The service may return fewer than this value, even if there are additional pages. If unspecified, at most 5
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`pageToken`	No	[query parameter] Optional. A page token, received from a previous `ListFirebaseLinks` call. Provide this to retrieve the subsequent page. When paginating, all other parameters p

Output Schema

Name	Required	Description	Default
`firebaseLinks`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 26, 2026

changedInput schema / properties / pageSize / description

Previous value: -"Optional. The maximum number of resources to return. The service may return fewer than this value, even if there are additional pages. If unspecified, at most 5"New value: +"[query parameter] Optional. The maximum number of resources to return. The service may return fewer than this value, even if there are additional pages. If unspecified, at most 5"

addedInput schema / properties / pageSize / format
```
Added value: +"int32"
```

changedInput schema / properties / pageToken / description

Previous value: -"Optional. A page token, received from a previous `ListFirebaseLinks` call. Provide this to retrieve the subsequent page. When paginating, all other parameters p"New value: +"[query parameter] Optional. A page token, received from a previous `ListFirebaseLinks` call. Provide this to retrieve the subsequent page. When paginating, all other parameters p"

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": {
+    "firebaseLinks": {
+      "items": {
+        "properties": {
+          "createTime": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "project": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextPageToken": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden; it does disclose the HTTP GET verb and how the request body is assembled (typed params win over `params`, or `body_file`). It omits permission requirements, pagination behavior beyond the pageToken schema, and does not explicitly say the operation is non-destructive.

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?

Front-loads the purpose in the first clause, then adds sibling routing and request-building mechanics. The request-construction sentence is somewhat boilerplate for a GET but is compact and not repetitive.

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 values need not be explained. Combined with a fully documented 7-parameter schema, the description covers enough for correct invocation; only auth/admin-scope prerequisites are unaddressed.

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 baseline is 3. The description echoes the typed-parameter precedence rule already stated in the `params` schema field and adds no new detail about `parent`, `pageSize`, `pageToken`, or `query`.

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: 'Lists FirebaseLinks on a property', and adds the constraint that a property can have at most one FirebaseLink. It names its siblings (create, delete) so the agent can distinguish the read variant, though it does not compare against the other list tools on properties (googleAdsLinks.list, dataStreams.list).

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 'Siblings over the same resource: create, delete' line implies the read/write split, and the 'at most one FirebaseLink' note hints this may be close to a get. But there is no explicit when-to-use versus the other property list tools, nor any stated prerequisites such as required scopes or parent format.

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

Deploy Server