Uptimepage

List status page viewers

list_status_page_viewers

Read-only

List who signed in to a private status page: each viewer's address, first and last visit, saved passkeys, whether they subscribe by email, and whether they are blocked; and for the page password, which names nobody, the devices signed in with it, its last sign-in and the wrong tries in 24 hours. Addresses are customer data. Read-only.

Input Schema

Name	Required	Description	Default
`slug`	Yes	The page slug (from `list_status_pages`).

Output Schema

Name	Required	Description	Default
`viewers`	Yes
`password`	No	`null` for a page never made private.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026

addedOutput schema / $defs / PagePasswordUse

Added value: +{
+  "description": "How the page password is used. Password visitors are anonymous, so this is\nall there is to see of them.",
+  "properties": {
+    "enabled": {
+      "type": "boolean"
+    },
+    "last_sign_in": {
+      "description": "Last sign-in with it, RFC 3339, if any.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sessions": {
+      "description": "Devices signed in with it now.",
+      "format": "int64",
+      "type": "integer"
+    },
+    "wrong_tries_24h": {
+      "description": "Wrong passwords tried in the last 24 hours.",
+      "format": "int64",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "enabled",
+    "sessions",
+    "wrong_tries_24h"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / password

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/PagePasswordUse"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "`null` for a page never made private."
+}

AddedOct 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The readOnlyHint annotation already covers the safety profile, yet the description adds real value beyond it: it flags 'Addresses are customer data' (a PII/privacy warning) and discloses the returned behavioral data such as blocked status and wrong-try counts. It stops short of describing auth/permission prerequisites for reading this sensitive data.

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?

Front-loaded with the verb and resource, and every clause names concrete return data or a constraint, so little is wasted. It is a single dense sentence, but it is appropriately sized for the amount of information conveyed.

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

Completeness4/5

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

With an output schema present, the description need not enumerate return values, yet it usefully previews them, and annotations carry the read-only guarantee. The only gap is the absence of guidance on prerequisites for accessing customer data on private pages.

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% and the single slug parameter is fully documented in the schema (including its provenance from list_status_pages), so the baseline of 3 applies. The description adds no additional meaning about the slug itself.

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?

States a specific verb and resource ('List who signed in to a private status page') and enumerates exactly what the result contains. It is clearly distinct from siblings such as list_status_pages and get_status_page, so an agent can pick it without opening a schema.

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 scopes applicability to private status pages, which implies when the tool is relevant, but it names no alternative and gives no explicit when-to-use/when-not guidance against siblings like get_status_page or list_status_pages.

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

All Uptimepage tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.