Retrieve Google Analytics 4 property details by providing the numeric property ID. Use this to access configuration and metadata for a specific GA4 property.
Get a GA4 property's details (by numeric property id, not measurement id).
| Name | Required | Description | Default |
|---|---|---|---|
| property_id | Yes | ||
| connection_id | No | ||
| session_token | No |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the behavioral burden. 'Get' clearly signals a read-only retrieval operation, and the property-id/measurement-id caveat adds useful operational context. Still, it does not mention error behavior, authentication needs, or what 'details' includes, leaving some behavioral ambiguity.
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 a single, focused sentence with no redundant wording. The most critical clarification—the id type—is front-loaded, making it easy for an agent to parse and act on.
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?
With no annotations, no output schema, and 0% parameter description coverage, the description is too sparse. It identifies the resource and the correct id format, which are essential, but it does not indicate return value shape, error conditions, or the purpose of the optional parameters, leaving a knowledgeable agent under-informed.
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 description coverage is 0%, so the description must compensate. It adds important meaning to property_id by specifying that it is a numeric property id and not a measurement id. However, connection_id and session_token are left completely unexplained, and no additional parameter context is provided beyond the schema's bare titles.
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 uses a specific verb ('Get') and resource ('GA4 property's details'), and explicitly disambiguates property id from measurement id. This makes the tool's function clear and distinguishes it from sibling list/report tools.
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?
The description implies when to use the tool: when you have a numeric GA4 property id and need the property's details. It also warns against using a measurement id. However, it does not explicitly mention alternatives or conditions for choosing another GA4 tool such as ga4_resolve or ga4_list_data_streams.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.