UI Verify

Page through the PR-vs-base changeset by kind

list_pr_stories

Read-only

Page through the PR-vs-base changeset stories of one kind (resolved by commitSha/prNumber/buildId) - use it to read past get_pr_changeset's first page. kind='new' returns stories the PR adds that the base branch has no baseline for; kind='changed' returns stories whose image differs from the base branch's accepted image (even if accepted mid-PR, with status=accepted); kind='removed' returns stories that HAD a baseline on the base branch but are gone from head (a deletion; each carries lastBuildId, not a review status or verdict). Returns { stories, nextCursor }: pass nextCursor back as cursor for the next page; null means no more. limit defaults to 25 (max 100). Requires the PR visual changeset feature.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes	Which changeset stories to page: new (added), changed (vs base), or removed (deleted).
`limit`	No	Page size (default 25, max 100).
`cursor`	No	The nextCursor from a prior page; omit for the first page.
`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
`stories`	Yes
`nextCursor`	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": {
    "nextCursor": {
      "type": [
        "string",
        "null"
      ]
    },
    "stories": {
      "items": {
        "anyOf": [
          {
            "additionalProperties": false,
            "properties": {
              "aiConfidence": {
                "type": [
                  "string",
                  "null"
                ]
              },
              "aiVerdict": {
                "type": [
                  "string",
                  "null"
                ]
              },
              "browsers": {
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              "kind": {
                "enum": [
                  "new",
                  "changed"
                ],
                "type": "string"
              },
              "name": {
                "type": "string"
              },
              "status": {
                "enum": [
                  "accepted",
                  "denied",
                  "ignored",
                  "pending"
                ],
                "type": "string"
              },
              "storyId": {
                "type": "string"
              },
              "title": {
                "type": "string"
              },
              "unstable": {
                "type": "boolean"
              },
              "viewports": {
                "items": {
                  "type": "string"
                },
                "type": "array"
              }
            },
            "required": [
              "storyId",
              "title",
              "name",
              "kind",
              "status",
              "browsers",
              "viewports",
              "aiVerdict",
              "aiConfidence",
              "unstable"
            ],
            "type": "object"
          },
          {
            "additionalProperties": false,
            "properties": {
              "browsers": {
                "items": {
                  "type": "string"
                },
                "type": "array"
              },
              "lastBuildId": {
                "format": "uuid",
                "type": "string"
              },
              "name": {
                "type": "string"
              },
              "storyId": {
                "type": "string"
              },
              "title": {
                "type": "string"
              },
              "viewports": {
                "items": {
                  "type": "string"
                },
                "type": "array"
              }
            },
            "required": [
              "storyId",
              "title",
              "name",
              "lastBuildId",
              "browsers",
              "viewports"
            ],
            "type": "object"
          }
        ]
      },
      "type": "array"
    }
  },
  "required": [
    "stories",
    "nextCursor"
  ],
  "type": "object"
}

First observedSep 5, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The annotations already mark the tool readOnly, and the description adds rich behavioral detail: kind-specific semantics, the accepted-mid-PR nuance, removed stories carrying lastBuildId instead of a verdict, cursor termination with null, and pagination limits. There is no contradiction with the readOnlyHint.

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?

The description is front-loaded with purpose and usage, and every sentence earns its place by adding meaningful detail. The kind definitions are dense but necessary because they distinguish subtle behaviors, and there is no filler or repetition.

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?

For a tool with six parameters, an output schema, and readOnly annotations, the description covers pagination, cursor handling, limits, resolver modes, kind semantics, and a feature requirement. Nothing an agent needs to invoke it correctly 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 goes further by explaining exactly what each kind means, how nextCursor should be passed back, and how resolution via commitSha/prNumber/buildId works. It does not explicitly state whether the resolver parameters are mutually exclusive, but the schema already documents each parameter clearly.

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 a specific action and resource: 'Page through the PR-vs-base changeset stories of one kind' and immediately names the resolver inputs. It also explicitly distinguishes the tool from get_pr_changeset by saying it is used to read past its first page, so an agent can tell them apart.

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 gives explicit guidance on when to use this tool: 'use it to read past get_pr_changeset's first page.' It also defines the three kind values and notes the feature prerequisite, giving an agent enough context to select the correct mode and avoid misuse.

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?