amendor-mcp

Publish preview

publish_preview

Idempotent

Marks a change request as ready for review by updating its status to 'in preview' and exposing the preview URL.

Instructions

Mark a change request ready for the requester to review. The preview is already live from the worktree; this flips status to "in preview" and surfaces the link.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "publish_preview"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Change request id whose local preview is ready.

Output Schema

Name	Required	Description
`id`	Yes	Change request id.
`status`	Yes	New status, set to "preview".
`review_url`	Yes	Page where the requester reviews and approves the change.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.4Jun 22, 2026

addedInput schema / properties / id / description

Added value: +"Change request id whose local preview is ready."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "description": "Change request id.",
+      "type": "string"
+    },
+    "review_url": {
+      "description": "Page where the requester reviews and approves the change.",
+      "type": "string"
+    },
+    "status": {
+      "description": "New status, set to \"preview\".",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "status",
+    "review_url"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jun 22, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds significant context beyond annotations: explains that the preview is already live, this flips status and surfaces a link. Annotations already indicate idempotent and non-destructive, description enriches with specific behavior.

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 concise sentences: first states purpose, second provides prerequisite and effect. No wasted words.

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 simple tool with one param, output schema present, and annotations covering safety, description fully explains purpose, behavior, and result. Complete for agent usage.

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 has 100% coverage with description for the single parameter 'id'. Description does not add extra meaning beyond the schema, baseline of 3 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?

Clearly states the action 'Mark a change request ready for the requester to review' and specifies the effect (flips status to 'in preview' and surfaces link). Distinguishes from siblings like set_preview_url and ship_change by noting the preview is already live.

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?

Implies usage after preview is live from worktree but does not explicitly state when not to use or provide alternatives. Clear context for a simple state transition.

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

Deploy Server