Skip to main content
Glama
devhelmhq

DevHelm MCP Server

Official
by devhelmhq
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

reorder_status_page_layout

Rearrange the complete status page layout by defining the new top-level section order and, when needed, component order inside groups to fix display sequence.

Instructions

Batch-reorder a status page's full layout.

Required: sections — top-level layout in their new order, where each entry is either {kind:"component", componentId} or {kind:"group", groupId}. Use groupOrders (optional) to also reorder components within specific groups; only include groups whose internal order changed. The full top-level set must be provided — partial reorders are rejected by the API.

Use this for "drag-and-drop" layout edits that touch both groups and ungrouped components. To reorder components within a single group only, prefer reorder_status_page_components.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
page_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.7.0
    • changedInput schema / properties / body / properties / groupOrders / anyOf
      Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "groupId": {
-          "description": "Group these components belong to",
-          "format": "uuid",
-          "type": "string"
-        },
-        "positions": {
-          "description": "Ordered component IDs with their within-group display order",
-          "items": {
-            "additionalProperties": false,
-            "properties": {
-              "componentId": {
-                "description": "Component ID",
-                "format": "uuid",
-                "type": "string"
-              },
-              "displayOrder": {
-                "description": "New display order (0-based)",
-                "type": "integer"
-              },
-              "groupId": {
-                "anyOf": [
-                  {
-                    "format": "uuid",
-                    "type": "string"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "default": null,
-                "description": "Target group ID, null for ungrouped"
-              }
-            },
-            "required": [
-              "componentId",
-              "displayOrder"
-            ],
-            "type": "object"
-          },
-          "minItems": 1,
-          "type": "array"
-        }
-      },
-      "required": [
-        "groupId",
-        "positions"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "properties": {
+        "groupId": {
+          "description": "Group these components belong to",
+          "format": "uuid",
+          "type": "string"
+        },
+        "positions": {
+          "description": "Ordered component IDs with their within-group display order",
+          "items": {
+            "properties": {
+              "componentId": {
+                "description": "Component ID",
+                "format": "uuid",
+                "type": "string"
+              },
+              "displayOrder": {
+                "description": "New display order (0-based)",
+                "type": "integer"
+              },
+              "groupId": {
+                "anyOf": [
+                  {
+                    "format": "uuid",
+                    "type": "string"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "default": null,
+                "description": "Target group ID, null for ungrouped"
+              }
+            },
+            "required": [
+              "componentId",
+              "displayOrder"
+            ],
+            "type": "object"
+          },
+          "minItems": 1,
+          "type": "array"
+        }
+      },
+      "required": [
+        "groupId",
+        "positions"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / body / properties / sections / items / additionalProperties
      Removed value: -false
  2. First observedv1.0.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description bears the behavioral disclosure burden. It discloses key API behavior: the full top-level section set is required, partial reorders are rejected, and groupOrders should only include groups whose internal order changed. It could go further on permissions or side effects, but the critical constraints are transparent.

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?

The description is compact and well structured: purpose first, then required payload rules, then usage alternatives. Every sentence carries useful information with no filler.

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

Completeness3/5

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

The description covers the main constraints and sibling routing, but the inaccurate section-entry shape and omission of required fields leave the agent without a fully reliable invocation contract. Output schema exists, so return values are less of a concern, but request construction is not complete enough.

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?

Reported schema description coverage is 0%, so the description must compensate. It explains the general purpose of sections and groupOrders, but it inaccurately describes each section entry as {kind:'component', componentId} or {kind:'group', groupId}, while the schema actually expects groupId/componentId/pageOrder. It also omits the required pageOrder field and says nothing about page_id, risking malformed calls.

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 opens with 'Batch-reorder a status page's full layout,' stating a specific verb, resource, and scope. It also distinguishes itself from the sibling reorder_status_page_components by clarifying that this tool handles full-layout reorders touching both groups and ungrouped components.

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?

Explicit guidance is given: use this tool for drag-and-drop edits affecting groups and ungrouped components, and prefer reorder_status_page_components for single-group reorders. It also warns that partial top-level reorders are rejected, which helps the agent decide if this tool fits.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/devhelmhq/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server