List GA4 properties for one account or across all accessible accounts, using an optional account ID to filter results.
List GA4 properties, optionally filtered to one account.
Args: account_id: numeric account id from ga4_list_accounts. Omit to list every property the credential can reach across all accounts.
| Name | Required | Description | Default |
|---|---|---|---|
| account_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It adds the scoping behavior (filter by account vs. all) but does not disclose potential limitations like pagination, rate limits, or response size. Since the tool is a straightforward read operation, the lack of harm details is partially mitigated by the verb 'List'.
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?
The description is compact—two sentences plus a clear args block. The main purpose is front-loaded, and the parameter explanation is neatly separated. No fluff or redundancy.
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 simple list tool with one optional parameter and an output schema (which presumably covers return values), the description provides all necessary context: what it does, the parameter's meaning and source, and the behavior when omitted. It is sufficient for an agent to call it correctly.
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?
Schema coverage is 0%, so the description must explain the parameter. It specifies that account_id is numeric and should come from ga4_list_accounts, and explains the omitted-case behavior. This adds crucial meaning beyond the bare schema (string or null). It does not give the exact format of the numeric string, but that is minor.
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?
The description states a specific verb ('List') and resource ('GA4 properties'), and clarifies the optional account filter. It naturally distinguishes itself from siblings like ga4_get_property (single property) and ga4_list_accounts (lists accounts).
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?
It explains when to use the optional account_id and that omitting it lists all reachable properties. It references ga4_list_accounts as the source of account IDs, implying a dependency. It does not explicitly name alternatives for when to avoid this tool, but the guidance is adequate for the simple use case.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.