Mark

Get GA4 Organic Overview

get_ga4_organic_overview

Read-onlyIdempotent

Reports Google Analytics organic search sessions, active users, and key events for a date range against the same number of days just before it, plus the top organic landing pages. Requires a connected Google Analytics property. Does not change anything. Related: get_search_performance, get_content_performance.

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

Input Schema

Name	Required	Description	Default
`to`	No	Range end YYYY-MM-DD.
`from`	No	Range start YYYY-MM-DD. Defaults to the last 28 settled days.

Output Schema

Name	Required	Description
`rows`	Yes
`appUrl`	Yes
`current`	Yes
`previous`	Yes
`consentNote`	Yes	Why GA4 reads lower than PostHog when the primary site waits for its cookie banner; null otherwise.
`topLandingPages`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedOutput schema / properties / consentNote

Added value: +{
+  "description": "Why GA4 reads lower than PostHog when the primary site waits for its cookie banner; null otherwise.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "appUrl",
-  "current",
-  "previous",
-  "rows",
-  "topLandingPages"
-]New value: +[
+  "appUrl",
+  "consentNote",
+  "current",
+  "previous",
+  "rows",
+  "topLandingPages"
+]

AddedOct 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavior beyond annotations: the tool compares against the immediately preceding equal-length period, includes top organic landing pages, and requires a connected GA property; it only mildly repeats 'Does not change anything.'

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 main capability is front-loaded in the first sentence, and the prerequisite is stated promptly. The description is compact, though 'Does not change anything' largely duplicates annotations and 'Related' is not actionable enough to fully earn its place.

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?

The tool has rich annotations, full schema description coverage, and an output schema, so the description need not explain return values. It covers what the report contains, the comparison period, and the GA connection requirement, leaving only minor gaps around alternative-tool selection and data freshness.

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%, so the schema already documents both date parameters and the default for 'from'. The description mentions the date range and comparison period but does not add parameter syntax or format details beyond the schema, making 3 the appropriate baseline.

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?

The description names a specific verb and resource set: Google Analytics organic search sessions, active users, key events, comparison period, and top organic landing pages. This is concrete enough to distinguish it from sibling performance tools even though it only lists them as related.

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?

It states a prerequisite, requiring a connected Google Analytics property, which is useful context. However, it does not explicitly say when to use this tool versus get_search_performance, get_content_performance, or other performance/overview siblings; 'Related' is not actual routing guidance.

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

All Mark 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?