ga_list_propertiesList all GA4 properties and their accounts accessible to the signed-in Google account. Use this to find property IDs for analytics reporting.
Lists every GA4 property (with its account) the signed-in Google account can access.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world scope are covered. The description adds one genuinely useful behavioral fact not in the annotations: results are bounded to properties the signed-in account can access, implying an auth requirement. It says nothing about pagination, result caps, or ordering.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that front-loads the verb and resource and appends the scoping qualifier. Every clause earns its place; there is no filler or restatement of the title.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read-only listing tool with full annotation coverage and no output schema, the description is nearly complete. The only meaningful omission is what the caller should do with the returned properties, e.g. feeding IDs into ga_report.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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; there is nothing for the description to disambiguate. The one scope statement present (account-visible properties) is a constraint, not a parameter, so no further compensation is required.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Lists every GA4 property') plus a precise scope ('the signed-in Google account can access'), and the parenthetical clarifies that account info comes along. It is clearly the discovery tool for GA properties versus ga_report/ga_realtime, though it never names a sibling to sharpen the distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance is given: nothing says this should be called first to obtain property IDs before ga_report, nor are there any preconditions or exclusions. The discovery nature of the tool is only implied by its name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.