ga4-mcp

Overview Schema Source Related Servers Discussions Admin

ga4_top_pages

Identify your most-viewed pages by returning page paths and titles ordered by page views, with configurable date range and result limit.

Instructions

Return top page paths and titles ordered by page views.

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

Input Schema

Name	Required	Default
`limit`	No
`end_date`	No	yesterday
`start_date`	No	28daysAgo
`property_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 6, 2026

TDQS

B3.1/5.0

Behavior3/5

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

There are no annotations, so the description bears the behavioral burden. It does signal a read-only retrieval operation and specifies ordering by page views, but it does not disclose behavior around result limits, date defaults, or required property context beyond what the schema already names.

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?

A single front-loaded sentence with no filler. It immediately conveys the output and ordering, which is all it attempts to communicate; the structure is as efficient as possible for the given content.

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?

With no annotations, no sibling differentiation, and no parameter guidance, the description is too thin for an agent to fully contextualize invocation. The output schema covers return shape, but selection logic and invocation expectations are underspecified.

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 adds no parameter meaning. It does not explain limit, date range semantics, or property_id requirements, leaving the schema's self-evident names and defaults to carry all parameter understanding.

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 clearly states a specific verb and resource: it returns top page paths and titles ordered by page views. It is distinguishable from siblings by naming a concrete report type, though it does not explicitly contrast itself with any sibling tool.

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 description implies usage: when an agent needs the most-viewed pages for a GA4 property. However, it provides no explicit guidance on when to choose this over alternatives like ga4_overview or ga4_run_report, and no exclusion criteria.

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

Deploy Server