umami-mcp

get_realtime

Retrieve real-time website analytics for the last 30 minutes, including current visitors, active URLs, referrers, countries, and events.

Instructions

Get real-time data for a website (last 30 minutes). Returns current visitors, active URLs, referrers, countries, and 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": {
      "websiteId": "<websiteId>"
    },
    "name": "get_realtime"
  }
}

Input Schema

Name	Required	Description
`path`	No
`unit`	No
`event`	No
`device`	No
`country`	No
`timezone`	No	IANA timezone
`websiteId`	Yes	Website UUID

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv2.1.1Oct 24, 2026

addedInput schema / properties / country
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / device
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / event
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / path
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / timezone

Added value: +{
+  "description": "IANA timezone",
+  "type": "string"
+}

addedInput schema / properties / unit

Added value: +{
+  "enum": [
+    "minute",
+    "hour",
+    "day",
+    "month",
+    "year"
+  ],
+  "type": "string"
+}

First observedv1.2.1Mar 19, 2026

TDQS

B3/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the time window and the categories of data returned, which is real behavioral information, but says nothing about result caps, ordering, whether filters narrow the 'current visitors' count, or read-vs-write status (implied read by 'Get').

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?

Two tight sentences, zero waste, with the scope-defining 'last 30 minutes' front-loaded before the payload list. Nothing to trim.

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?

Seven parameters, no annotations, no output schema, and five undocumented parameters — this is exactly the case where the description has to do the heavy lifting. It covers the return shape conceptually but leaves filtering semantics, defaults and response limits unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 29%: path, unit, event, device and country have no descriptions anywhere. The description's mention of 'active URLs, referrers, countries, and events' faintly hints that path/country/event act as filters, but it never explains units, timezone, or how multiple filters combine, so the coverage gap is left unfilled.

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?

States a specific verb and resource ('Get real-time data for a website') plus a scope ('last 30 minutes') and enumerates what comes back (visitors, URLs, referrers, countries, events). The only gap is that it never distinguishes itself from the sibling get_active_visitors, which reads like an overlapping capability.

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?

The '(last 30 minutes)' parenthetical implicitly frames the window, but there is no statement of when to pick this over get_active_visitors, get_stats, get_pageviews or get_sessions. No prerequisites, no exclusions, no alternative named.

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

Deploy Server