amendor-mcp

List change requests

list_change_requests

Read-onlyIdempotent

List change requests submitted by end users on your sites. Filter by status to view open, accepted, or shipped requests.

Instructions

List change requests submitted by end users on sites you ship. Optionally filter by status. Start here to see what people are asking for.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No	Optional status filter: new, accepted, building, preview, approved, shipped, or rejected. Omit to list every open request.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`requests`	Yes	Matching change requests, newest first.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.4Jun 22, 2026

addedInput schema / properties / status / description

Added value: +"Optional status filter: new, accepted, building, preview, approved, shipped, or rejected. Omit to list every open request."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "requests": {
+      "description": "Matching change requests, newest first.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "description": "Change request id; pass to get_change_request.",
+            "type": "string"
+          },
+          "page_url": {
+            "description": "URL of the page the request was made on.",
+            "type": "string"
+          },
+          "request_text": {
+            "description": "What the user asked for, in their own words.",
+            "type": "string"
+          },
+          "status": {
+            "description": "Current status of the request.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "status",
+          "request_text",
+          "page_url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "requests"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jun 22, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint false. The description adds no behavioral traits beyond these, such as pagination or ordering. It does not contradict annotations.

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 sentences with no extraneous words: first sentence states purpose and filter, second provides guidance. Front-loaded and efficient.

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?

Given the simple tool (one optional param, output schema present), the description covers the core functionality. It omits details like result ordering or limits, but these are not critical for a straightforward list tool.

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% with a full description of the status parameter and its values. The description only echoes 'Optionally filter by status,' adding no new meaning.

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 clearly states the tool lists change requests submitted by end users, with optional status filtering. It distinguishes from sibling tools like get_change_request (single request) and update_status (status update).

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?

The description advises 'Start here to see what people are asking for,' implying it's the entry point for viewing requests. It does not explicitly contrast with alternatives or mention when not to use, but the sibling tool names provide context.

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

Deploy Server