gsc-ga4-mcp

Overview Schema Source Related Servers Discussions Admin

ga4_landing_pages

Get Google Analytics 4 landing page performance with engagement metrics for a specified date range. Provide start and end dates to retrieve key user interaction data.

Instructions

GA4 landing pages with engagement metrics.

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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "ga4_landing_pages"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`endDate`	Yes	YYYY-MM-DD
`property`	No	GA4 property, e.g. properties/123456789 or 123456789
`startDate`	Yes	YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 24, 2026

TDQS

D1.5/5.0

Behavior1/5

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

No annotations are provided, so the description must fully disclose behavior, but it does not. There is no mention of what data is returned, whether it is read-only, any rate limits, or side effects. The description offers zero behavioral transparency.

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

Conciseness2/5

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

The description is extremely short but this is under-specification, not conciseness. It provides a terse noun phrase that lacks actionable structure. There is no front-loading of critical information—only a vague label.

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

Completeness1/5

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

With 4 parameters, no output schema, and no annotations, this tool demands a much richer description to explain its purpose, output format, and any limitations. The current description is wholly inadequate for an agent to call this tool reliably, especially given the large sibling set with overlapping capabilities.

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

Parameters2/5

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

The description adds no information about parameters beyond what the schema already provides. While schema coverage is 75%, the description does not clarify semantics for the 'property' parameter or the date formats. It fails to compensate for any gaps, and the minimal mention of 'engagement metrics' does not relate to any parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'GA4 landing pages with engagement metrics' is essentially a restatement of the tool name, providing no verb or specific action (e.g., 'retrieve', 'list', 'analyze'). It is vague about what engagement metrics are returned and how this tool differs from siblings like ga4_top_pages or ga4_run_report.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus any of the 19 siblings. No context about use cases, prerequisites, or exclusions is provided. An agent cannot determine if this is the right tool for a given task without external knowledge.

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