AdLoop

Analytics property overview

get_ga4_property

Read-only

Show a GA4 property's configuration in one call: details, linked Google Ads accounts, data streams and data retention.

Returns the property's display name, time zone, currency, industry, service level (standard or 360), type and create time; every linked Google Ads account (customer ID, whether it is a manager account, personalized advertising); every data stream with its measurement ID or app ID; how many months event and user data are kept; and the number of key events. insights[] flags settings that cost data: two-month retention, no Google Ads link while key events exist, the configured Ads account not being linked, a property in the trash. A part the user may not read is listed under unavailable instead of failing the call. Reads the GA4 Admin API (properties.get, googleAdsLinks.list, dataStreams.list, getDataRetentionSettings, keyEvents.list).

Google Analytics Data API: https://developers.google.com/analytics/devguides/reporting/data/v1 and Admin API: https://developers.google.com/analytics/devguides/config/admin/v1

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

Input Schema

Name	Required	Description	Default
`property_id`	No	GA4 property as "properties/123456789" or the bare numeric ID (see get_account_summaries). If empty, uses the default from config.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive), and the description adds genuinely non-obvious behavior: a part of the property the user cannot read is returned under `unavailable` rather than failing the call, and `insights[]` flags cost-relevant misconfigurations. It omits any mention of pagination or per-endpoint quota behavior for the four underlying list calls, which is a meaningful gap for a fan-out read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one-line purpose, then a structured enumeration of returned fields, then the insights semantics, then the source APIs. The return-value enumeration is somewhat redundant given an output schema exists, but each clause is informative and the whole thing stays navigable.

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?

Given an output schema exists, the description need not explain return shapes, yet it covers partial-permission failure handling, the meaning of insights flags, and the exact Admin API methods being fanned out. Nothing material an agent needs to call this correctly is missing.

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 description coverage is 100% and the single parameter already documents both accepted forms ("properties/123456789" or bare numeric ID), the empty-means-config-default behavior, and the get_account_summaries pointer. The description adds nothing further about the parameter, so baseline 3 applies.

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?

Opens with a specific verb+resource ("Show a GA4 property's configuration in one call") and then enumerates exactly what is retrieved: property details, linked Google Ads accounts, data streams, retention, key events. This clearly distinguishes it from siblings like audit_ga4_property (which analyzes) or list_key_events (which lists one slice).

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?

"In one call" implicitly tells the agent this consolidates multiple Admin API reads, which is useful context against siblings such as list_key_events or get_account_summaries. However, it never explicitly says when to prefer it over audit_ga4_property or the individual list tools, and gives no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AdLoop tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.