Skip to main content
Glama
Sign In
ga4-mcp-server

ga4-mcp-server

by dienhokhanh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

List GA4 accounts

list_accounts
Read-only

Retrieve Google Analytics accounts accessible to the authenticated user, including each GA4 property's ID and display name. Use this when the property ID is unknown.

Instructions

List the Google Analytics accounts the authenticated user can access, each with its GA4 properties (ID and display name). Start here when you don't know the property ID.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and scope are covered structurally. The description adds useful context by specifying the result is scoped to the authenticated user's accessible accounts and that each account nests its properties — meaningful beyond the annotations, though no pagination or result-size behavior is mentioned.

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?

Two compact sentences with zero waste. The resource and scope lead, and the routing hint ("Start here...") is placed at the end where it is most actionable.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no input parameters, no output schema, and safety already covered by annotations, the description supplies exactly what is missing: what the tool returns (accounts plus nested properties with ID and display name) and when to reach for it. Nothing needed to invoke it correctly is absent.

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?

Zero parameters, so there is nothing to document; baseline for a parameterless tool is 4. The description correctly implies no filtering inputs are needed.

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?

States a specific verb (List) and resource (Google Analytics accounts the authenticated user can access), and clarifies the returned payload includes GA4 properties with ID and display name. This clearly separates it from siblings like list_properties and get_property.

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?

"Start here when you don't know the property ID" gives an explicit entry-point condition and implicitly contrasts with get_property for when the ID is known. It doesn't name the alternative tool explicitly or state exclusions, so it falls just short of a 5.

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