Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_ga4_top_pages

Rank GA4 landing pages by sessions, conversions, or users to identify which pages drive traffic and signups, with prior-period comparisons for performance changes.

Instructions

GA4 metrics per page (landing / URL), ranked so you see which pages drive the most sessions, signups (conversions) or users. Every row returns the page plus sessions, users, conversions and engagement_rate, each with the prior-period prev and change_pct. Sort by sessions (default), conversions or users; capped by limit (default 25, max 100). The page-level companion to get_ga4_traffic_by_source.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does well on output shape (page, sessions, users, conversions, engagement_rate, plus prev and change_pct per metric) and on defaults (limit 25, max 100; sort defaults to sessions). It says nothing about date-range scoping, permissions, row-limit behavior when truncating, or how prior-period is determined, which leaves real behavioral gaps for a reporting tool.

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

Conciseness5/5

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

Three tight sentences: what it ranks, what each row contains, then controls and the companion pointer. Purpose and return shape are front-loaded with no filler.

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 and no annotations, the description must explain returns and behavior, and it largely does: field list, comparison metrics, sortable fields, and limit bounds. The missing pieces are date-range scoping and what happens at the row cap, both relevant for a ranked analytics query.

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?

The input schema is an empty object with additionalProperties, so the description is the only source of parameter meaning, and it supplies the sort enum options, the default sort, the limit default and the max cap. It does not explain how a date range or the landing-vs-URL dimension is selected, so it is not fully compensating.

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: GA4 per-page metrics ranked by sessions, conversions or users. The parenthetical '(landing / URL)' pins down the dimension, and the closing line positions it against get_ga4_traffic_by_source so the agent can distinguish a page-level report from a source-level one.

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

Usage Guidelines4/5

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

Names the sibling it complements ('the page-level companion to get_ga4_traffic_by_source'), which implicitly tells the agent to pick this one for page/URL breakdowns rather than channel breakdowns. It stops short of an explicit 'use X instead when' rule or stating prerequisites.

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