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

ga4-mcp-server

by dienhokhanh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Get GA4 property details

get_property
Read-only

Retrieve a Google Analytics 4 property's settings including time zone, currency, industry category, service level, creation time, and parent account via property ID, resource name, or display name.

Instructions

Get a GA4 property's settings: time zone, currency, industry category, service level (Standard/360), creation time and parent account.

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": "get_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertyNoGA4 property: numeric ID ("123456789"), resource name ("properties/123456789") or display name ("My Website"). Defaults to GA4_DEFAULT_PROPERTY if set.

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 and the description does not need to restate it. The description adds genuine value by naming the exact settings returned, but says nothing about auth requirements, whether the entity exists, or error behavior for an unknown property.

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?

One tightly written sentence, front-loaded with the verb and resource, with the returned fields packed into a colon list. Nothing extraneous.

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 getter with no output schema, enumerating the returned settings in the description is exactly the compensation needed. The only unaddressed element is what happens on failure/unknown property, which is minor here.

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 coverage is 100% and the single 'property' parameter already documents the three accepted formats plus the GA4_DEFAULT_PROPERTY fallback. The description adds no parameter-level detail beyond the schema, 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 ('Get a GA4 property's settings') and enumerates the exact fields returned (time zone, currency, industry category, service level, creation time, parent account), making the scope concrete. It does not explicitly name sibling tools like list_properties, so an agent must infer that this is the single-property fetch rather than a listing.

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?

Usage is implied by the wording — you call this to read one property's configuration — but there is no explicit when-to-use/when-not guidance or pointer to alternatives such as list_properties or get_metadata. Minimum viable, with a clear gap.

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