UI Verify

Accept, deny, or ignore one story's change

review_diff

Destructive

Record a review on a single diff result (get diffResultId from get_build/get_diff). 'accept' makes the candidate the new baseline for that story on its branch, so the next build is clean; 'deny' records the rejection without changing the baseline; 'ignore' excludes the story from the gate persistently (the snapshot keeps differing on future builds but no longer flags the check) — use it for an intentional, ongoing diff like an animation or a live timestamp. This is the same accept/deny/ignore as the dashboard, attributed to the agent (and to you, when you logged in). Use after you've inspected the diff (e.g. with render_diff_image) and decided intended vs. regression. accept and ignore are refused while the story has an unresolved review comment, including one left on an earlier build of the branch (read it with list_comments, address it, resolve_comment the thread, then retry); deny is always allowed.

Input Schema

Name	Required	Description	Default
`decision`	Yes	'accept' advances the baseline; 'deny' records a rejection; 'ignore' excludes the story from the gate.
`diffResultId`	Yes	The diff result id from get_build or get_diff.

Output Schema

Name	Required	Description
`decision`	Yes
`diffResultId`	Yes
`openReviewComments`	No	Present when open review comments are waiting on some branch of this project; read yours with list_comments.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 8, 2026

addedOutput schema / properties / openReviewComments

Added value: +{
+  "additionalProperties": false,
+  "description": "Present when open review comments are waiting on some branch of this project; read yours with list_comments.",
+  "properties": {
+    "branches": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "branch": {
+            "type": "string"
+          },
+          "lastActivityAt": {
+            "type": "string"
+          },
+          "open": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "branch",
+          "open",
+          "lastActivityAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "branchesTotal": {
+      "type": "number"
+    },
+    "hint": {
+      "type": "string"
+    },
+    "projectId": {
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "branches",
+    "branchesTotal",
+    "projectId",
+    "hint"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "decision": {
+      "enum": [
+        "accepted",
+        "denied",
+        "ignored"
+      ],
+      "type": "string"
+    },
+    "diffResultId": {
+      "format": "uuid",
+      "type": "string"
+    }
+  },
+  "required": [
+    "diffResultId",
+    "decision"
+  ],
+  "type": "object"
+}

First observedSep 5, 2026

TDQS

Score is being calculated.

All UI Verify tools Inspect

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

Need Help?