UI Verify

Get what changed in a UI Verify build

get_build

Read-only

Triage one build, resolved by commitSha, prNumber, or buildId (exactly one). Returns the gate verdict and counts (total/changed/failed/unchanged), then the FIRST page (25) of the changed stories (story id, viewport, % pixels changed, review decision, the AI verdict aiVerdict=intended|regression + aiConfidence, and for a regression the judge's one-line aiFlagReason=what-looks-unintended, when AI review is on, and the story's own review-comment tally comments {total, unresolved}) and the first page of failed stories (failedStories[].kind is render when the story produced no frame, or interaction when it rendered and its play() assertion threw; failedStories[].error is the message's first line, errorTruncated marks the ones that carried more). When AI review ran, aiReview tallies how many changes look like regressions vs intended, and the changed list is ordered likely-regressions-first. changedNextCursor / failedNextCursor are non-null when there are more than 25: page the rest with list_build_stories. counts.unchanged is how many stories did NOT change and have a baseline - this triage call does NOT list them (keeps the response lean); call list_build_stories status=unchanged to browse them (e.g. to confirm a passed build's stories are 'identical to baseline'). comments is the build-wide review-comment tally {total, unresolved}: unresolved>0 means a designer/QA (or another agent) left an open note on a story - read it with list_comments BEFORE you accept. No image URLs here - call get_diff or render_diff_image for pixels.

Input Schema

TableJSON Schema

Name	Required	Description
`buildId`	No	Resolve this exact build id.
`prNumber`	No	Resolve the latest build for this PR number.
`commitSha`	No	Resolve the build for this git commit SHA.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`branch`	Yes
`counts`	Yes
`status`	Yes
`buildId`	Yes
`aiReview`	Yes
`comments`	Yes
`prNumber`	Yes
`commitSha`	Yes
`createdAt`	Yes
`gateStatus`	Yes
`failedStories`	Yes
`changedStories`	Yes
`failedNextCursor`	Yes
`autoAcceptChanges`	Yes
`changedNextCursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

addedOutput schema / properties / changedStories / items / properties / comments

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "total": {
+      "$ref": "#/properties/comments/properties/total"
+    },
+    "unresolved": {
+      "$ref": "#/properties/comments/properties/unresolved"
+    }
+  },
+  "required": [
+    "total",
+    "unresolved"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / changedStories / items / required

Previous value: -[
-  "diffResultId",
-  "storyId",
-  "title",
-  "name",
-  "viewport",
-  "browser",
-  "changedPct",
-  "decision",
-  "isNew",
-  "unstable",
-  "aiVerdict",
-  "aiClassification",
-  "aiIntroducedBy",
-  "aiConfidence",
-  "aiSummary",
-  "aiFlagReason"
-]New value: +[
+  "diffResultId",
+  "storyId",
+  "title",
+  "name",
+  "viewport",
+  "browser",
+  "changedPct",
+  "decision",
+  "isNew",
+  "unstable",
+  "aiVerdict",
+  "aiClassification",
+  "aiIntroducedBy",
+  "aiConfidence",
+  "aiSummary",
+  "aiFlagReason",
+  "comments"
+]

Changed2 schema fields changedSep 16, 2026

addedOutput schema / properties / comments

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "total": {
+      "type": "number"
+    },
+    "unresolved": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "unresolved"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "buildId",
-  "commitSha",
-  "branch",
-  "prNumber",
-  "status",
-  "gateStatus",
-  "autoAcceptChanges",
-  "createdAt",
-  "counts",
-  "aiReview",
-  "changedStories",
-  "changedNextCursor",
-  "failedStories",
-  "failedNextCursor"
-]New value: +[
+  "buildId",
+  "commitSha",
+  "branch",
+  "prNumber",
+  "status",
+  "gateStatus",
+  "autoAcceptChanges",
+  "createdAt",
+  "counts",
+  "comments",
+  "aiReview",
+  "changedStories",
+  "changedNextCursor",
+  "failedStories",
+  "failedNextCursor"
+]

First observedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=true, and the description consistently describes a read operation, aligning with that. The description goes beyond annotations by detailing response structure, pagination cursors, ordering (likely-regressions-first), and that no image URLs are included—calling out get_diff or render_diff_image for pixels. This adds significant behavioral transparency.

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 long but information-dense, with every sentence adding necessary detail for an agent to understand the tool's behavior. It is front-loaded with the main purpose and return structure, but includes a lot of detail in one paragraph, which could be improved with more structured formatting, but given the complexity it remains efficient.

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?

The description is highly complete for the tool's complexity. It covers resolution methods, response format, pagination, ordering, exclusions, and guidance on related tools. With an output schema present, return values are documented elsewhere, and the description fills in all behavioral gaps, making it fully usable by an agent without additional research.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all three parameters are already documented. However, the description adds critical selection constraints: exactly one of buildId, prNumber, or commitSha must be provided. This is not explicit in the schema's individual descriptions but is essential for correct invocation, justifying a score above the baseline of 3.

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's purpose: triage one build resolved by one of three identifiers, returning gate verdict, counts, and first pages of changed and failed stories. It distinguishes itself from sibling tools like list_build_stories by explicitly noting pagination is handled elsewhere and that unchanged stories are not listed here.

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 provides clear usage context: it explains that list_build_stories should be used for pagination and for browsing unchanged stories, and that list_comments should be read before acceptance when unresolved comments exist. It does not explicitly state when not to use this tool versus alternatives, but the context is strong.

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

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.