SEOctopus

Overview Schema Source Related Servers Discussions Admin

analytics_pages

Retrieve per-page Google Analytics metrics: pageviews, engagement, bounce rate, conversions. Filter by date range and sort by any metric.

Instructions

Get per-page analytics 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": {
      "propertyId": "<propertyId>"
    },
    "name": "analytics_pages"
  }
}

Input Schema

Name	Required	Description	Default
`propertyId`	Yes	GA4 property ID
`dateRange`	No	Date range	last28days
`orderBy`	No	Sort order	pageviews
`limit`	No	Number of pages to return

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations exist, so the description must bear the burden. It does not disclose whether the operation is read-only, idempotent, requires authentication, or has rate limits. This is insufficient for a safe agent invocation.

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 that efficiently conveys the core purpose with no extraneous information. Every word earns its place.

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?

Lacks output schema or description of return format. Given the complexity of analytics data (multiple metrics, pagination), the description is too minimal to fully prepare the agent for handling results.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no additional meaning beyond the parameter names and defaults; baseline 3 is appropriate.

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 it retrieves page-level analytics metrics, distinguishing it from sibling tools like analytics_overview (aggregate) or analytics_realtime (real-time). However, it could specify the metric types more explicitly, though the orderBy parameter hints at them.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs. alternatives. While the name and description imply per-page usage, there is no explicit context or exclusion criteria, leaving the agent without decision support.

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