Skip to main content
Glama
Sign In
Google Analytics MCP Server

Google Analytics MCP Server

Official
by googleanalytics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_account_summaries

Read-only

Retrieves Google Analytics account and property summaries so you can identify available accounts and properties before running reports.

Instructions

Retrieves information about the user's Google Analytics accounts and properties.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_account_summaries"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0
  2. Removedv0.5.0
  3. Changed2 schema fields changedv0.3.0
    • removedInput schema / title
      Removed value: -"get_account_summariesArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_account_summariesOutput",
-  "type": "object"
-}New value: +null
  4. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds nothing beyond that — no mention of authentication/authorization requirements for reading Google Analytics data, pagination behavior for accounts with many properties, or the shape of the returned summaries.

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?

A single, front-loaded sentence with no wasted words. It is appropriately sized for a zero-parameter read tool, though the brevity borders on under-specification given the available space.

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?

For a zero-param read-only tool with full annotation coverage and no output schema, the description is minimally adequate. It is missing the practically important context that this is the discovery step supplying IDs for the report-running siblings, which is the main thing an agent needs to know beyond the annotations.

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?

The tool takes zero parameters, so the baseline is 4. The input schema is empty and fully consistent with the description, leaving nothing parameter-related to explain.

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+resource: retrieves Google Analytics accounts and properties. It is clear what the tool returns, but it never distinguishes itself from sibling tools like get_property_details or list_google_ads_links, so an agent must guess which discovery tool to call first.

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?

There is no when-to-use guidance, no mention of alternatives, and no note that this is typically the entry point for obtaining account/property IDs needed by run_report and the other sibling tools. The agent gets no routing signal at all.

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