Skip to main content
Glama

Google Analytics landing pages

analytics_landing_pages
Read-only

Analyze GA4 landing page performance by sessions, users, engagement rate, key events, and key event rate; filter by channel or date to see which pages drive traffic and conversions.

Instructions

Where visitors land and whether it works: sessions, users, engagement rate, key events (GA4's conversions) and key event rate per landing page, most sessions first. Pass channel to see one source, e.g. "Paid Search" for Google Ads traffic or "Organic Search". Changes nothing.

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": "analytics_landing_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days, ending yesterday
limitNoMost landing pages to return
channelNoOnly sessions whose default channel group contains this, e.g. Paid Search, Organic Search, Direct
end_dateNoExact last day, YYYY-MM-DD
start_dateNoExact first day, YYYY-MM-DD
property_idYesGA4 property id, digits only (from analytics_properties)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.46.0
    • changedInput schema / properties / start_date / description
      Previous value: -"Exact first day, YYYY-MM-DD. Pass with end_date to use exact dates instead of days"New value: +"Exact first day, YYYY-MM-DD"
  2. Addedv0.15.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and 'Changes nothing' largely restates that. The genuinely additive behavioral detail is the result ordering ('most sessions first') and the implied default look-back window, which go beyond the structured fields but leave return shape and pagination behavior unaddressed.

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?

Two tight sentences, front-loaded with what the tool returns and the ordering, followed by the filter hint. The closing 'Changes nothing' is redundant against the readOnlyHint annotation and is the only dead weight.

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?

With no output schema, the description correctly enumerates the metric columns returned and the sort order, and the schema covers the date-window and limit defaults. An agent could call this correctly from the definition alone, though the relationship to analytics_report remains unstated.

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 coverage is 100%, so each parameter is already documented, which sets the baseline at 3. The description adds a little meaning for the channel parameter by mapping 'Paid Search' to Google Ads traffic, but adds nothing about days, limit, or the start/end date pair beyond what the schema states.

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 names the specific resource (landing pages) and enumerates the returned metrics (sessions, users, engagement rate, key events, key event rate), plus the sort order 'most sessions first'. That distinguishes it from generic siblings like analytics_report, though it does not name any sibling explicitly.

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?

The opening phrase 'Where visitors land and whether it works' implies the analysis use case, and the channel example ('Paid Search' for Google Ads traffic) tells the agent how to narrow scope. However, there is no explicit statement of when to prefer this over analytics_report or landing_page_speed, nor any when-not guidance.

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