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 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'). 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
`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. Dates show when Glama detected each change.

Changed1 schema field changedSep 5, 2026

changedOutput schema / (root)

Before

null

After

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "aiReview": {
      "anyOf": [
        {
          "additionalProperties": false,
          "properties": {
            "intended": {
              "type": "number"
            },
            "regressions": {
              "type": "number"
            },
            "reviewed": {
              "type": "number"
            }
          },
          "required": [
            "regressions",
            "intended",
            "reviewed"
          ],
          "type": "object"
        },
        {
          "type": "null"
        }
      ]
    },
    "autoAcceptChanges": {
      "type": "boolean"
    },
    "branch": {
      "type": "string"
    },
    "buildId": {
      "format": "uuid",
      "type": "string"
    },
    "changedNextCursor": {
      "type": [
        "string",
        "null"
      ]
    },
    "changedStories": {
      "items": {
        "additionalProperties": false,
        "properties": {
          "aiClassification": {
            "type": [
              "string",
              "null"
            ]
          },
          "aiConfidence": {
            "type": [
              "string",
              "null"
            ]
          },
          "aiFlagReason": {
            "type": [
              "string",
              "null"
            ]
          },
          "aiIntroducedBy": {
            "type": [
              "string",
              "null"
            ]
          },
          "aiSummary": {
            "type": [
              "string",
              "null"
            ]
          },
          "aiVerdict": {
            "type": [
              "string",
              "null"
            ]
          },
          "browser": {
            "type": "string"
          },
          "changedPct": {
            "type": [
              "number",
              "null"
            ]
          },
          "decision": {
            "type": [
              "string",
              "null"
            ]
          },
          "diffResultId": {
            "format": "uuid",
            "type": "string"
          },
          "isNew": {
            "type": "boolean"
          },
          "name": {
            "type": "string"
          },
          "storyId": {
            "type": "string"
          },
          "title": {
            "type": "string"
          },
          "unstable": {
            "type": "boolean"
          },
          "viewport": {
            "type": "string"
          }
        },
        "required": [
          "diffResultId",
          "storyId",
          "title",
          "name",
          "viewport",
          "browser",
          "changedPct",
          "decision",
          "isNew",
          "unstable",
          "aiVerdict",
          "aiClassification",
          "aiIntroducedBy",
          "aiConfidence",
          "aiSummary",
          "aiFlagReason"
        ],
        "type": "object"
      },
      "type": "array"
    },
    "commitSha": {
      "type": "string"
    },
    "counts": {
      "additionalProperties": false,
      "properties": {
        "changed": {
          "type": "number"
        },
        "failed": {
          "type": "number"
        },
        "total": {
          "type": "number"
        },
        "unchanged": {
          "type": "number"
        }
      },
      "required": [
        "total",
        "changed",
        "failed",
        "unchanged"
      ],
      "type": "object"
    },
    "createdAt": {
      "type": "string"
    },
    "failedNextCursor": {
      "type": [
        "string",
        "null"
      ]
    },
    "failedStories": {
      "items": {
        "additionalProperties": false,
        "properties": {
          "browser": {
            "type": "string"
          },
          "error": {
            "type": "string"
          },
          "errorTruncated": {
            "type": "boolean"
          },
          "kind": {
            "enum": [
              "render",
              "interaction"
            ],
            "type": "string"
          },
          "name": {
            "type": "string"
          },
          "storyId": {
            "type": "string"
          },
          "title": {
            "type": "string"
          },
          "viewport": {
            "type": "string"
          }
        },
        "required": [
          "storyId",
          "title",
          "name",
          "viewport",
          "browser",
          "error",
          "errorTruncated",
          "kind"
        ],
        "type": "object"
      },
      "type": "array"
    },
    "gateStatus": {
      "type": "string"
    },
    "prNumber": {
      "type": [
        "number",
        "null"
      ]
    },
    "status": {
      "type": "string"
    }
  },
  "required": [
    "buildId",
    "commitSha",
    "branch",
    "prNumber",
    "status",
    "gateStatus",
    "autoAcceptChanges",
    "createdAt",
    "counts",
    "aiReview",
    "changedStories",
    "changedNextCursor",
    "failedStories",
    "failedNextCursor"
  ],
  "type": "object"
}

First observedSep 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only mark the call read-only, so the description carries the behavioral burden and fully delivers: first-page truncation at 25, changed and failed story semantics, AI verdict fields, ordering by likely regressions first, non-null cursor behavior, and explicit omission of unchanged stories. No contradiction with annotations.

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 and dense, but every block of detail earns its place: pagination, excluded unchanged stories, image routing, and output-field semantics all affect correct invocation. The main structural flaw is that much of this is packed into run-on sentences with heavy parentheticals.

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 definition covers the triage scope, response pagination, omitted data, related-tool handoffs, and failure-mode distinctions, while an output schema handles the raw return shape. Nothing an agent needs to decide whether and how to call get_build is missing.

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 description coverage is 100%, so the baseline is 3; the description adds genuine value by asserting the exactly-one constraint among the otherwise all-optional parameters and by clarifying that prNumber/commitSha resolve to a build. It does not add per-parameter details beyond that, hence 4 rather than 5.

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 'Triage one build' and specifies the exact resource (a UI Verify build) and resolution keys (commitSha, prNumber, or buildId, exactly one), then enumerates the return contents. This clearly distinguishes get_build from siblings like list_builds and list_build_stories, which handle collections or paging.

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?

It explicitly routes follow-up actions: page beyond 25 with list_build_stories, browse unchanged stories with list_build_stories status=unchanged, and fetch images from get_diff or render_diff_image. It also states why unchanged stories are omitted, so an agent can decide when this tool is the right entry point.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0

Disambiguation5/5

Each tool targets a distinct concern: list vs get vs pagination, build triage vs PR changeset, diff URL vs inline pixels, single-review vs bulk-accept. The descriptions explicitly call out the differences between similar-sounding tools, so an agent can reliably choose the right one.

Naming Consistency5/5

All tool names follow a consistent lowercase verb_noun pattern: get_* for single entities, list_* for collections, and review_diff/accept_build for actions. There are no mixed conventions or vague verbs.

Tool Count5/5

Nine tools fit the visual regression review workflow well: discovery, triage, pagination, image inspection, and reviewing. Each tool fills a distinct role without redundancy, and the count is in the sweet spot for an agent to keep all tool purposes in context.

Completeness5/5

The surface covers the full review lifecycle: find builds, triage changed/failed/unchanged stories, paginate, inspect diffs as URLs or inline images, review per-diff, and bulk-accept an entire build. The PR-changeset tools also cover cross-PR questions and deletion cases that would otherwise be dead ends.

Resources

Need Help?