Skip to main content
Glama
Sign In
ga4-mcp

ga4-mcp

by onionst
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

ga4_acquisition

Identify traffic sources and campaign effectiveness by retrieving session channels and source/medium data for any GA4 property and date range.

Instructions

Return session channels and source/medium acquisition performance.

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_id": "<property_id>"
    },
    "name": "ga4_acquisition"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
end_dateNoyesterday
start_dateNo28daysAgo
property_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says 'Return,' which implies a read-only operation, but gives no detail about pagination, date-range behavior, data granularity, or output shape. This is minimal and leaves important behavioral context undisclosed.

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 description is a single, waste-free sentence that front-loads the core action and resource. It earns its place as far as it goes, though extreme brevity limits how much value the sentence provides.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 4 parameters, no annotations, and only a vague description, this is not complete. The presence of an output schema reduces the need to explain return values, but the description still fails to situate the tool among siblings, clarify date range semantics, or explain property_id's role.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention property_id, start_date, end_date, or limit. It only hints at the result dimensions (session channels, source/medium), which does not compensate for the complete lack of parameter-level meaning.

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?

The description uses a specific verb ('Return') and names the resource/scope ('session channels and source/medium acquisition performance'), making the tool's purpose understandable. However, it does not explicitly differentiate it from sibling tools like ga4_top_pages or ga4_events beyond the 'acquisition' framing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as ga4_realtime or ga4_overview. There are no exclusions, prerequisites, or conditions stated, leaving the agent to infer usage entirely from the tool name and minimal wording.

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