fettle-mcp

Overview Schema Source Related Servers Discussions Admin

List status pages

list_status_pages

Read-onlyIdempotent

List an organization's public status pages to find the page id required before posting an incident; supports page, size, and sort controls.

Instructions

List the organization's public status pages. Each has id, slug, name, description, is_published (publicly visible now), history_days, created_at, groups (each with name, position and its components) and ungrouped_components. Use it to find a page's id before posting an incident on it. For one page use get_status_page; pages are created and edited only in the dashboard. Returns a page of results: items plus total, page, size and pages.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number, 1 or more; default 1.
`size`	No	Rows per page, 1 to 100; default 25. Keep paging until you have seen total rows.
`sort`	No	created_at (the default, newest first) or name.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`size`	Yes
`items`	Yes
`pages`	Yes
`total`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.6.1Oct 20, 2026

addedInput schema / properties / page / description

Added value: +"Page number, 1 or more; default 1."

addedInput schema / properties / size / description

Added value: +"Rows per page, 1 to 100; default 25. Keep paging until you have seen total rows."

addedInput schema / properties / sort / description

Added value: +"created_at (the default, newest first) or name."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "items": {
+      "items": {
+        "properties": {
+          "created_at": {
+            "type": "string"
+          },
+          "description": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "groups": {
+            "items": {
+              "properties": {
+                "components": {
+                  "items": {
+                    "properties": {
+                      "display_name": {
+                        "anyOf": [
+                          {
+                            "type": "string"
+                          },
+                          {
+                            "type": "null"
+                          }
+                        ]
+                      },
+                      "id": {
+                        "format": "uuid",
+                        "type": "string"
+                      },
+                      "monitor_id": {
+                        "format": "uuid",
+                        "type": "string"
+                      },
+                      "position": {
+                        "type": "integer"
+                      }
+                    },
+                    "required": [
+                      "id",
+                      "monitor_id",
+                      "display_name",
+                      "position"
+                    ],
+                    "type": "object"
+                  },
+                  "type": "array"
+                },
+                "id": {
+                  "format": "uuid",
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                },
+                "position": {
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "id",
+                "name",
+                "position",
+                "components"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "history_days": {
+            "type": "integer"
+          },
+          "id": {
+            "format": "uuid",
+            "type": "string"
+          },
+          "is_published": {
+            "type": "boolean"
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "ungrouped_components": {
+            "items": {
+              "properties": {
+                "display_name": {
+                  "anyOf": [
+                    {
+                      "type": "string"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                },
+                "id": {
+                  "format": "uuid",
+                  "type": "string"
+                },
+                "monitor_id": {
+                  "format": "uuid",
+                  "type": "string"
+                },
+                "position": {
+                  "type": "integer"
+                }
+              },
+              "required": [
+                "id",
+                "monitor_id",
+                "display_name",
+                "position"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "id",
+          "slug",
+          "name",
+          "description",
+          "is_published",
+          "history_days",
+          "created_at",
+          "groups",
+          "ungrouped_components"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "page": {
+      "type": "integer"
+    },
+    "pages": {
+      "type": "integer"
+    },
+    "size": {
+      "type": "integer"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "items",
+    "total",
+    "page",
+    "size",
+    "pages"
+  ],
+  "type": "object"
+}

First observedv0.5.4Oct 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare a safe, idempotent, read-only operation, so the description only needs to add context beyond that. It usefully adds that pages are public, lists returned fields, and explains the paginated result shape, though some field detail overlaps with the output schema.

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?

The description is front-loaded and efficient, with the primary purpose and alternative tool stated early. The returned-field enumeration is somewhat detailed but still relevant to the task.

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?

Given an output schema and full annotation coverage, the description supplies enough context for an agent to call the tool correctly. It covers purpose, alternative, pagination behavior, and creation/edit constraints.

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%, and the parameters page, size, and sort are already documented in the schema. The description does not add syntax or selection guidance beyond the schema, so the baseline 3 is appropriate.

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 gives a specific verb and resource: listing the organization's public status pages. It also distinguishes this list operation from the sibling get_status_page for a single page.

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

Usage Guidelines5/5

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

It explicitly states the main use case: finding a page's id before posting an incident. It also names get_status_page as the alternative for one page and clarifies that creation and editing happen only in the dashboard.

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

Deploy Server