Skip to main content
Glama

Uptimepage

by dev.uptimepage
OverviewDiscussionsAdmin

Create status page

create_status_page

Create a status page. It is created unpublished unless you pass enabled, so its components can be curated before anyone can read it. The slug is the page's public address: it is first-come across the platform and moving it later breaks every existing link, so confirm it with the user rather than inventing one. Pass access with protected true to make it private: only the listed domains and addresses can open it, after signing in with a code sent to their email (Team plan). Add monitors to it with add_status_page_components. Not read-only.

Input Schema

NameRequiredDescriptionDefault
nameYesPage display name, at most 80 characters.
slugYesURL slug, lowercase. This is the page's public address and cannot be guessed back later, so pick it deliberately.
accessNoMake it private from the start. Omit for a public page.
enabledNoDefaults to false: a page is created dark so components can be curated before anyone can read it.

Output Schema

NameRequiredDescriptionDefault
nameYes
slugYes
accessNoWho may open it, or null for a page never made private.
enabledYes
public_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • removedInput schema / $defs / PageAccessArg / properties / email / default / session_days
      Removed value: -null
    • addedInput schema / $defs / PageAccessArg / properties / password
      Added value: +{
+  "$ref": "#/$defs/PagePasswordAccessArg",
+  "default": {
+    "enabled": false
+  }
+}
    • changedInput schema / $defs / PageAccessArg / properties / protected / description
      Previous value: -"Private when true: only the addresses and domains in `rules` can open\nthe page, by signing in on it with a code sent to their email. False\nmakes it public again and keeps the list for next time."New value: +"Private when true: only people a way in lets through can open the\npage: the addresses and domains in `rules`, by a code sent to their\nemail, or anyone with the page password. False makes it public again\nand keeps the list and the password for next time."
    • changedInput schema / $defs / PageAccessArg / properties / rules / description
      Previous value: -"Who can open it, up to 500 entries. Read back, these are customer data."New value: +"Who can get an email code, up to 500 entries. Read back, these are\ncustomer data."
    • addedInput schema / $defs / PageAccessArg / properties / session_days
      Added value: +{
+  "default": null,
+  "description": "Keep a sign-in, by email or password, for 7, 30 or 90 days. Omit to\nkeep it until sign-out.",
+  "format": "int32",
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • changedInput schema / $defs / PageEmailAccessArg / properties / enabled / description
      Previous value: -"Defaults to true; a private page needs it."New value: +"Defaults to true. A private page needs it or the password."
    • removedInput schema / $defs / PageEmailAccessArg / properties / session_days
      Removed value: -{
-  "default": null,
-  "description": "Keep a sign-in for 7, 30 or 90 days. Omit to keep it until sign-out.",
-  "format": "int32",
-  "type": [
-    "integer",
-    "null"
-  ]
-}
    • addedInput schema / $defs / PagePasswordAccessArg
      Added value: +{
+  "additionalProperties": false,
+  "description": "The page password way in. The password itself never passes through here:\nit is set in the app, the API or Terraform.",
+  "properties": {
+    "enabled": {
+      "default": false,
+      "description": "Anyone with the page password can open the page. Turning it on needs\none already set; turning it off keeps it and signs out everyone who\ncame in with it.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
    • removedOutput schema / $defs / PageAccessArg / properties / email / default / session_days
      Removed value: -null
    • addedOutput schema / $defs / PageAccessArg / properties / password
      Added value: +{
+  "$ref": "#/$defs/PagePasswordAccessArg",
+  "default": {
+    "enabled": false
+  }
+}
    • changedOutput schema / $defs / PageAccessArg / properties / protected / description
      Previous value: -"Private when true: only the addresses and domains in `rules` can open\nthe page, by signing in on it with a code sent to their email. False\nmakes it public again and keeps the list for next time."New value: +"Private when true: only people a way in lets through can open the\npage: the addresses and domains in `rules`, by a code sent to their\nemail, or anyone with the page password. False makes it public again\nand keeps the list and the password for next time."
    • changedOutput schema / $defs / PageAccessArg / properties / rules / description
      Previous value: -"Who can open it, up to 500 entries. Read back, these are customer data."New value: +"Who can get an email code, up to 500 entries. Read back, these are\ncustomer data."
    • addedOutput schema / $defs / PageAccessArg / properties / session_days
      Added value: +{
+  "default": null,
+  "description": "Keep a sign-in, by email or password, for 7, 30 or 90 days. Omit to\nkeep it until sign-out.",
+  "format": "int32",
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • changedOutput schema / $defs / PageEmailAccessArg / properties / enabled / description
      Previous value: -"Defaults to true; a private page needs it."New value: +"Defaults to true. A private page needs it or the password."
    • removedOutput schema / $defs / PageEmailAccessArg / properties / session_days
      Removed value: -{
-  "default": null,
-  "description": "Keep a sign-in for 7, 30 or 90 days. Omit to keep it until sign-out.",
-  "format": "int32",
-  "type": [
-    "integer",
-    "null"
-  ]
-}
    • addedOutput schema / $defs / PagePasswordAccessArg
      Added value: +{
+  "additionalProperties": false,
+  "description": "The page password way in. The password itself never passes through here:\nit is set in the app, the API or Terraform.",
+  "properties": {
+    "enabled": {
+      "default": false,
+      "description": "Anyone with the page password can open the page. Turning it on needs\none already set; turning it off keeps it and signs out everyone who\ncame in with it.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Changed5 schema fields changed
    • addedInput schema / $defs
      Added value: +{
+  "PageAccessArg": {
+    "additionalProperties": false,
+    "description": "Who may open a status page; the same shape as the REST `access` field. As a\nwrite it replaces what is stored, whole.",
+    "properties": {
+      "email": {
+        "$ref": "#/$defs/PageEmailAccessArg",
+        "default": {
+          "enabled": true,
+          "passkeys_enabled": true,
+          "recheck_days": null,
+          "session_days": null
+        }
+      },
+      "protected": {
+        "description": "Private when true: only the addresses and domains in `rules` can open\nthe page, by signing in on it with a code sent to their email. False\nmakes it public again and keeps the list for next time.",
+        "type": "boolean"
+      },
+      "rules": {
+        "default": [],
+        "description": "Who can open it, up to 500 entries. Read back, these are customer data.",
+        "items": {
+          "$ref": "#/$defs/PageAccessRuleArg"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "protected"
+    ],
+    "type": "object"
+  },
+  "PageAccessRuleArg": {
+    "additionalProperties": false,
+    "description": "One access list entry.",
+    "properties": {
+      "kind": {
+        "description": "`domain` lets in every address at `value` (`example.com`); `address`\nlets in one person (`name@example.com`).",
+        "type": "string"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "value"
+    ],
+    "type": "object"
+  },
+  "PageEmailAccessArg": {
+    "additionalProperties": false,
+    "description": "The emailed-code way in, and the passkeys that shortcut it.",
+    "properties": {
+      "enabled": {
+        "default": true,
+        "description": "Defaults to true; a private page needs it.",
+        "type": "boolean"
+      },
+      "passkeys_enabled": {
+        "default": true,
+        "description": "Let viewers save a passkey after an email sign-in. Defaults to true.",
+        "type": "boolean"
+      },
+      "recheck_days": {
+        "default": null,
+        "description": "Ask passkey viewers for an email code again after 30, 90 or 365 days.\nOmit to never ask.",
+        "format": "int32",
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "session_days": {
+        "default": null,
+        "description": "Keep a sign-in for 7, 30 or 90 days. Omit to keep it until sign-out.",
+        "format": "int32",
+        "type": [
+          "integer",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / access
      Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/PageAccessArg"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Make it private from the start. Omit for a public page."
+}
    • addedOutput schema / $defs
      Added value: +{
+  "PageAccessArg": {
+    "additionalProperties": false,
+    "description": "Who may open a status page; the same shape as the REST `access` field. As a\nwrite it replaces what is stored, whole.",
+    "properties": {
+      "email": {
+        "$ref": "#/$defs/PageEmailAccessArg",
+        "default": {
+          "enabled": true,
+          "passkeys_enabled": true,
+          "recheck_days": null,
+          "session_days": null
+        }
+      },
+      "protected": {
+        "description": "Private when true: only the addresses and domains in `rules` can open\nthe page, by signing in on it with a code sent to their email. False\nmakes it public again and keeps the list for next time.",
+        "type": "boolean"
+      },
+      "rules": {
+        "default": [],
+        "description": "Who can open it, up to 500 entries. Read back, these are customer data.",
+        "items": {
+          "$ref": "#/$defs/PageAccessRuleArg"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "protected"
+    ],
+    "type": "object"
+  },
+  "PageAccessRuleArg": {
+    "additionalProperties": false,
+    "description": "One access list entry.",
+    "properties": {
+      "kind": {
+        "description": "`domain` lets in every address at `value` (`example.com`); `address`\nlets in one person (`name@example.com`).",
+        "type": "string"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "value"
+    ],
+    "type": "object"
+  },
+  "PageEmailAccessArg": {
+    "additionalProperties": false,
+    "description": "The emailed-code way in, and the passkeys that shortcut it.",
+    "properties": {
+      "enabled": {
+        "default": true,
+        "description": "Defaults to true; a private page needs it.",
+        "type": "boolean"
+      },
+      "passkeys_enabled": {
+        "default": true,
+        "description": "Let viewers save a passkey after an email sign-in. Defaults to true.",
+        "type": "boolean"
+      },
+      "recheck_days": {
+        "default": null,
+        "description": "Ask passkey viewers for an email code again after 30, 90 or 365 days.\nOmit to never ask.",
+        "format": "int32",
+        "type": [
+          "integer",
+          "null"
+        ]
+      },
+      "session_days": {
+        "default": null,
+        "description": "Keep a sign-in for 7, 30 or 90 days. Omit to keep it until sign-out.",
+        "format": "int32",
+        "type": [
+          "integer",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  }
+}
    • addedOutput schema / properties / access
      Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/PageAccessArg"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Who may open it, or null for a page never made private."
+}
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and the description reinforces 'Not read-only' while adding genuine context beyond them: the unpublished-by-default state, the platform-wide first-come slug semantics with link-breakage warning, the private-access sign-in flow with email codes (Team plan), and the password caveat that the secret never passes through this call.

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?

Five dense sentences, front-loaded with purpose and default state before drilling into slug and access semantics. Every sentence carries information relevant to correct invocation, though the access/plan parenthetical is slightly heavy for a description of this length.

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 values need no explanation, and the description covers the remaining gaps: the default unpublished state, slug permanence and uniqueness, privacy semantics, and the follow-up tool for adding monitors. An agent has everything needed to call it correctly.

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 coverage is 100%, so the baseline is 3; the description nonetheless adds meaning the schema does not carry, such as the platform-wide slug uniqueness and the instruction to confirm it with the user, plus the practical effect of enabling the page and of setting access.protected=true. This is additive rather than redundant.

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 ('Create a status page') and immediately distinguishes its scope from siblings by naming the companion tool add_status_page_components for monitor attachment. An agent can tell this apart from update_status_page or create_monitor without opening any schema.

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 clear operating context: pages are created dark, add components separately, and confirm the slug with the user rather than inventing one. It stops short of explicitly naming when to prefer update_status_page or the conditions under which creation should be refused (e.g., slug collision handling), but the when-to guidance is strong.

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

All Uptimepage toolsInspect
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.

Resources