AdCopilot

GA4: read attribution settings

ga4_get_attribution_settings

Read-onlyIdempotent

Read a GA4 property's attribution settings (properties/): the reporting attribution model, the lookback window for first-visit and first-open key events and for the other key events, and which channels may earn credit for web conversions shared with Google Ads. Returns Google's answer and a plain summary of the four.

Tools revision: d80f65c0.

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

Input Schema

Name	Required	Description	Default
`property`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuine content beyond that: the returned data includes both Google's raw answer and a 'plain' summary of the four settings, and it flags the cross-product dependency on a Google Ads link for channel-credit data.

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?

The purpose and the returned fields are front-loaded in two compact sentences with no filler. The trailing 'Tools revision: d80f65c0.' line is build metadata that adds nothing for an agent and slightly dilutes the definition.

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 read-only, single-parameter tool with an output schema present, the description covers purpose, scope of returned settings, and the Google Ads link caveat. Minor gaps remain around the exact property id format and behavior when attribution settings are unavailable, but nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the single 'property' parameter is a bare string with a title only. The description compensates by indicating the resource-name shape '(properties/<id>)', which tells the agent this is a GA4 property resource rather than an account or numeric-only id, though it stops short of an unambiguous example.

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?

States a specific verb and resource ('Read a GA4 property's attribution settings') and enumerates the exact contents: reporting attribution model, lookback windows for first-visit/first-open and other key events, and shared Google Ads channel credit. This clearly separates it from the sibling ga4_update_attribution_settings, which writes 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 only implied — an agent can infer it should call this before ga4_update_attribution_settings or when auditing attribution configuration, but the description never says so. There are no stated prerequisites (e.g. property must be linked to Google Ads to see channel credit) and no explicit alternatives.

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

All AdCopilot 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.

Resources

Need Help?