Skip to main content
Glama
Sign In
ga4-mcp

ga4-mcp

by onionst
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ga4_list_properties

Identify every Google Analytics 4 property available with your current read-only credentials for reporting.

Instructions

List every GA4 property accessible with the current read-only credentials.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly communicates that the operation is read-only and scoped to the current credentials, and that it returns the full set of accessible properties. It does not detail pagination or ordering, but the output schema covers return structure.

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?

The description is a single sentence with no filler. The action is front-loaded, and every word adds meaning: 'List', 'every', 'accessible', and 'current read-only credentials' all contribute to the tool's purpose and scope.

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?

For a zero-parameter listing tool with an output schema, this description is complete. It states what is returned, the scope of results, and the authentication context. Nothing needed for correct invocation is missing.

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 has zero parameters, and the schema already covers 100% of the parameter space. The description's mention of 'every GA4 property accessible with the current read-only credentials' clarifies that no user-supplied parameters are needed beyond the implicit authentication context.

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?

The description uses a specific verb ('List') and a clear resource ('every GA4 property accessible'), making the tool's purpose immediately obvious. It also distinguishes itself from sibling reporting tools by indicating this is an account-level discovery operation rather than a data-reporting operation.

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?

The description gives clear context: it lists all GA4 properties under the current read-only credentials. It does not explicitly name alternatives or exclusion conditions, but among the siblings none performs the same listing function, so the intended use is evident.

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