SEOctopus

Overview Schema Source Related Servers Discussions Admin

analytics_realtime

Retrieve realtime Google Analytics data including active users, page views, and events. Monitor current site activity instantly.

Instructions

Get realtime Google Analytics data: active users, pages, events

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

Input Schema

Name	Required	Description	Default
`propertyId`	Yes	GA4 property ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so the description must carry full burden. It mentions 'Get' implying read-only, but lacks any behavioral details such as data freshness, rate limits, authentication requirements, or limitations of realtime data. The description is insufficient for transparency.

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?

Description is a single sentence that is concise and front-loaded with key information. It is efficient but lacks structure for more complex information. Acceptable for a simple tool.

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?

Given no output schema and a single required parameter, the description should provide more context about return data format or behavior. It only lists data types, leaving agents uninformed about response structure or other important details.

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% with one parameter described as 'GA4 property ID'. The description adds no additional meaning beyond the schema, so it meets the baseline but does not enhance understanding of the parameter.

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?

The description clearly states the verb 'Get', the resource 'realtime Google Analytics data', and specifies the data types: active users, pages, events. This distinguishes it from sibling tools like analytics_overview or analytics_pages which are not realtime.

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 versus alternatives like analytics_traffic or analytics_pages. The description only states what it does without context of when realtime data is appropriate or how it differs from non-realtime siblings.

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