Skip to main content
Glama
Samarth GTM MCP Server

Samarth GTM MCP Server

Official

ga4_data_retention_get

Retrieve a GA4 property's data retention settings, including event data retention duration and whether retention resets on new activity. Read-only.

Instructions

Get the data retention settings for a GA4 property (event data retention duration and whether retention resets on new activity). Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "property": "<property>"
    },
    "name": "ga4_data_retention_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertyYesGA4 property ID, e.g. "123456789" or "properties/123456789".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.497.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / property / minLength
      Removed value: -1
    • addedInput schema / properties / property / pattern
      Added value: +"^\\s*(properties\\/)?\\d+\\s*$"
  2. Addedv1.421.0
  3. Removedv1.350.0
  4. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description does carry the safety profile by stating 'Read-only', which is the key behavioral trait for a settings read. It does not disclose permission requirements, error behavior for invalid properties, or the shape of the response beyond naming the two settings.

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 compact sentence that front-loads the action and resource, names the returned fields parenthetically, and closes with the read-only qualifier. No redundant or filler text.

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 single-parameter read with a fully described schema and no output schema, the description covers purpose, scope, and read-only nature adequately. A brief note on what happens with an unknown property or what permissions are needed would close the remaining gap.

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 is fully documented in the schema with an example and accepted pattern, so the baseline of 3 applies. The description adds no extra meaning about the property parameter (e.g., where to obtain the ID) beyond what the schema already states.

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?

Specific verb+resource: 'Get the data retention settings for a GA4 property', and it names the two fields returned (event data retention duration and reset-on-activity flag). It is clearly distinguished from the sibling ga4_update_data_retention, which mutates the same settings.

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 rather than stated: the read-only framing and the 'Get' verb suggest inspection before calling ga4_update_data_retention, but no explicit when-to-use or when-not-to-use guidance is given. No prerequisites (e.g., required permissions) are mentioned.

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