Skip to main content
Glama

Honeyfield Marketing MCP

GA4: Top pages

ga4_top_pages
Read-only

Meistbesuchte Seiten: pagePath x screenPageViews, sessions, engagementRate. Zeitraum: letzte N Tage inkl. heute. Max. limit Zeilen (höchstens 500) — die Zeilensumme ist nicht die Gesamtzahl; Gesamtwerte über ga4_report mit dimensions=[]. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

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

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
workspaceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=true), yet the description still adds real behavioral facts: the window includes today, limit is capped at 500, the row count is not the site total, and workspace may be omitted for single-workspace accounts. This is exactly the kind of constraint an agent needs beyond the annotations.

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?

Four compact, front-loaded clauses — metrics first, then time window, then row-limit caveat, then workspace note. Every sentence carries information; the density is high but nothing is redundant.

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

Completeness5/5

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

With an output schema present, return structure need not be described, and the remaining hazards an agent faces — time window definition, row-limit semantics, grain of aggregation, workspace selection, and the aggregation escape hatch — are all covered.

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?

Schema description coverage is 0%, so the description carries the full burden and does so for all three parameters: days is defined as the last-N-days window including today, limit is bounded at 500, and workspace is a customer slug that is optional when only one workspace exists. Only the interaction between limit and the default of 20 is left implicit.

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?

Names the exact resource (pagePath) and the metrics returned (screenPageViews, sessions, engagementRate), so an agent knows precisely what report this produces. It also points to ga4_report for aggregate totals, which differentiates it from that sibling, though it does not distinguish itself from other top-N style tools (sc_top_pages, bing_top_pages).

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?

Gives an explicit routing rule: this tool returns a limited row set, and totals must be obtained via ga4_report with dimensions=[]. The default time window (last N days including today) is stated. Missing is guidance on when to prefer GA4 vs. Search Console or Bing top-pages tools, but within the GA4 family the usage context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources