Skip to main content
Glama
Google Growth MCP

Google Growth MCP

by kremnyi

ga4_list_account_summaries

List all Google Analytics accounts and their GA4 properties available to the authenticated user, so you can identify which properties to query or manage.

Instructions

List every Google Analytics account and GA4 property available to the authenticated account.

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": "ga4_list_account_summaries"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose the key scoping fact that results are limited to the authenticated account, and "List" implies a non-mutating read. It omits pagination, ordering, and result-shape behavior, which matters since no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, and the scope qualifier ("available to the authenticated account") is front-loaded at the end of the leading clause. Nothing is repeated from the tool name unnecessarily.

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-argument, no-annotation list tool the description covers the essentials of what it does and whose data it sees. What is missing is what an "account summary" actually contains versus a full property object, which an agent would need since there is no output schema. Adequate but with a noticeable gap.

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 there is no parameter meaning to add and the description cannot be faulted for gaps here. Baseline of 4 applies for a parameterless tool.

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?

Names a specific verb ("List") and a specific resource pair ("Google Analytics account and GA4 property"), scoped to the authenticated account. An agent can distinguish this discovery-style tool from reporting siblings like ga4_run_report. It stops short of explicitly contrasting with ga4_get_metadata, which is the closest conceptual neighbor.

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?

Usage is only implied: listing accounts and properties is naturally a prerequisite step before running reports, but the description never says when to call it or what to call instead for metadata. No exclusions or alternatives are named, so the agent must infer the workflow position itself.

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