Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

analyticsadmin.accounts.list

Lists all Google Analytics accounts accessible to the caller, excluding trashed accounts by default, to help identify available accounts for administration.

Instructions

Returns all accounts accessible by the caller. Note that these accounts might not currently have GA properties. Soft-deleted (ie: "trashed") accounts are excluded by default. Returns an empty list if no relevant accounts are found. Note: The easiest way to retrieve a list of all properties you have access to is by using ListAccountSummaries [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: delete, get, getDataSharingSettings, patch, provisionAccountTicket, runAccessReport, searchChangeHistoryEvents.

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.
dry_runNoReturn the request that would be sent, without sending it.
pageSizeNo[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_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 `ListAccounts` call. Provide this to retrieve the subsequent page. When paginating, all other parameters provid
showDeletedNo[query parameter] Whether to include soft-deleted (ie: "trashed") Accounts in the results. Accounts can be inspected to determine whether they are deleted or not.

Output Schema

NameRequiredDescriptionDefault
accountsNo
nextPageTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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 `ListAccounts` call. Provide this to retrieve the subsequent page. When paginating, all other parameters provid"New value: +"[query parameter] Optional. A page token, received from a previous `ListAccounts` call. Provide this to retrieve the subsequent page. When paginating, all other parameters provid"
    • changedInput schema / properties / showDeleted / description
      Previous value: -"Whether to include soft-deleted (ie: \"trashed\") Accounts in the results. Accounts can be inspected to determine whether they are deleted or not."New value: +"[query parameter] Whether to include soft-deleted (ie: \"trashed\") Accounts in the results. Accounts can be inspected to determine whether they are deleted or not."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "accounts": {
+      "items": {
+        "properties": {
+          "createTime": {
+            "type": "string"
+          },
+          "deleted": {
+            "type": "boolean"
+          },
+          "displayName": {
+            "type": "string"
+          },
+          "gmpOrganization": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "regionCode": {
+            "type": "string"
+          },
+          "updateTime": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextPageToken": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/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 and does add real value: soft-deleted accounts are excluded by default, an empty list is returned when nothing matches, and accounts may lack GA properties. It does not cover auth requirements, pagination behavior, or result ordering.

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?

The account-specific content is front-loaded and useful, but the trailing boilerplate about JSON request bodies, typed flags winning over params, body_file, and a sibling enumeration is largely irrelevant for a GET/list call and dilutes the definition.

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 no explanation, and schema docs cover all seven parameters. Combined with the explicit default-exclusion and empty-result notes, an agent has enough to call it correctly; only pagination guidance is implied rather than stated.

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 coverage is 100%, so the baseline is 3; the schema already documents pageSize, pageToken and showDeleted. The description only reinforces the showDeleted default behavior and says nothing extra about pagination or the generic query/params escape hatches.

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 opening sentence gives a specific verb and resource (returns all accounts accessible by the caller) and the note explicitly routes property-listing to the sibling ListAccountSummaries, so the tool is distinguishable from accountSummaries.list.

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 clearly states the retrieval use case and points to the alternative (ListAccountSummaries) for property access. It lacks an explicit 'don't use this when' statement, but the alternative naming gives strong context.

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