Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

analyticsadmin.accountSummaries.list

Retrieve summaries of every Google Analytics account the caller can access, with pagination for large result sets.

Instructions

Returns summaries of all accounts accessible by the caller [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

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 AccountSummary resources to return. The service may return fewer than this value, even if there are additional pages. If unspeci
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 `ListAccountSummaries` call. Provide this to retrieve the subsequent page. When paginating, all other parameter

Output Schema

NameRequiredDescriptionDefault
nextPageTokenNo
accountSummariesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / pageSize / description
      Previous value: -"Optional. The maximum number of AccountSummary resources to return. The service may return fewer than this value, even if there are additional pages. If unspeci"New value: +"[query parameter] Optional. The maximum number of AccountSummary resources to return. The service may return fewer than this value, even if there are additional pages. If unspeci"
    • addedInput schema / properties / pageSize / format
      Added value: +"int32"
    • changedInput schema / properties / pageToken / description
      Previous value: -"Optional. A page token, received from a previous `ListAccountSummaries` call. Provide this to retrieve the subsequent page. When paginating, all other parameter"New value: +"[query parameter] Optional. A page token, received from a previous `ListAccountSummaries` call. Provide this to retrieve the subsequent page. When paginating, all other parameter"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "accountSummaries": {
+      "items": {
+        "properties": {
+          "account": {
+            "type": "string"
+          },
+          "displayName": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "propertySummaries": {
+            "items": {
+              "properties": {
+                "canEdit": {
+                  "type": "boolean"
+                },
+                "displayName": {
+                  "type": "string"
+                },
+                "parent": {
+                  "type": "string"
+                },
+                "property": {
+                  "type": "string"
+                },
+                "propertyType": {
+                  "enum": [
+                    "PROPERTY_TYPE_UNSPECIFIED",
+                    "PROPERTY_TYPE_ORDINARY",
+                    "PROPERTY_TYPE_SUBPROPERTY",
+                    "PROPERTY_TYPE_ROLLUP"
+                  ],
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextPageToken": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose '[HTTP GET]' (signaling a safe read) and explains request-body construction mechanics, but it omits auth requirements, pagination behavior, and what 'accessible by the caller' entails. The body_file guidance is generic boilerplate that is arguably irrelevant for a GET list endpoint.

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 purpose is front-loaded in a single clear sentence. The second sentence is long and generic boilerplate about JSON and request bodies that does not earn its place for this specific GET list endpoint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 coverage is full. However, with no annotations and no usage guidance, the description leaves gaps around pagination expectations, authentication, and how this differs from accounts.list.

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 six parameters thoroughly. The description merely repeats the typed-parameters-win-over-params-map rule and the body_file override, adding no new meaning beyond 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 ('Returns'), resource ('summaries of all accounts'), and scope ('accessible by the caller'). It does not explicitly differentiate from the closely named sibling analyticsadmin.accounts.list, but an agent can tell what resource is returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description only describes what the tool returns; it gives no indication of when to use this versus alternatives like accounts.list or properties.list, nor any conditions or exclusions.

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