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

ga4-mcp-server

by dienhokhanh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

List GA4 properties

list_properties
Read-only

Retrieve a flat list of accessible GA4 properties, optionally filtered by account ID, account name, or property name search. Use to discover available Google Analytics 4 properties for reporting.

Instructions

List accessible GA4 properties as a flat list. Optionally filter by account (ID or name) or by a case-insensitive search on the property name.

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_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoCase-insensitive substring of the property display name.
accountNoAccount ID or (partial) account display name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond that: 'accessible' discloses permission-scoped results, and 'flat list' discloses that results are not nested by account. It does not mention pagination, result caps, or return shape, so it is useful but not rich.

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 sentences with zero filler; the core action and its scoping ('flat list') are front-loaded, followed by the optional filters. Every clause carries information.

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?

For a simple read-only list with a 2-param, fully documented schema and no output schema, the description covers what an agent needs to select and invoke it. Minor omissions (pagination behavior, whether an empty result is possible) are the only gaps.

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 both parameters (search, account) are already fully documented in the schema, including ID-or-name and case-insensitive semantics. The description restates the same behavior without adding syntax, format, or edge-case detail, so the baseline 3 applies.

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 and resource ('List accessible GA4 properties') and adds scope detail ('as a flat list'), which implicitly contrasts with hierarchical or single-property siblings like get_property and list_accounts. However, it never names a sibling explicitly, so the differentiation must be inferred.

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?

The optional filters hint at usage context ('optionally filter by account... or by search'), implying this is the browse/discovery tool for properties. But there is no explicit when-to-use guidance versus list_accounts or get_property, and no stated prerequisites (e.g., which permissions surface which properties).

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