Skip to main content
Glama

UI Verify

by io.github.igrlk

Page through a build's stories by status

list_build_stories
Read-only

Page through one build's stories filtered by status (resolved by commitSha/prNumber/buildId). Use it to read past get_build's first page, or to browse the unchanged/passed stories get_build only counts. status='changed' returns changed stories (same shape + order as get_build, regression-first); status='failed' returns failed stories; status='unchanged' returns the stories that did NOT change this build but have a baseline on this branch (storyId, viewport, browser) - fetch any of their images by storyId with get_diff or render_diff_image to confirm 'identical to baseline'. Returns { stories, nextCursor }: pass nextCursor back as cursor for the next page; null means no more. limit defaults to 25 (max 100). Unchanged is only available once the build has settled (an in-progress build has rendered nothing, so it returns an empty page).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size (default 25, max 100).
cursorNoThe nextCursor from a prior page; omit for the first page.
statusYesWhich stories to page: changed, failed, or unchanged (baselined, didn't change this build).
buildIdNoResolve this exact build id.
prNumberNoResolve the latest build for this PR number.
commitShaNoResolve the build for this git commit SHA.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
storiesYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

The description discloses behavior far beyond the annotations: what each status returns, ordering for changed stories, cursor semantics with nextCursor, default/max limit, and the edge case that unchanged stories are only available after the build settles. This is rich, non-obvious 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?

The description is dense but every clause earns its place. It front-loads the purpose, then covers status behaviors, return shape, paging, limits, and a timing edge case without redundant filler.

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 complete for a paginated read-only tool: it explains return shape, pagination, status-specific semantics, build resolution, and the important unsettled-build behavior. No significant gap remains for an agent to call it correctly.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds substantial meaning: it explains the exact meaning of each status value, how cursor should be passed back, how build resolution works via commitSha/prNumber/buildId, and the limit default. This goes well beyond the bare schema descriptions.

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 states a specific verb and resource: page through one build's stories filtered by status. It also distinguishes itself from get_build by noting it reads past get_build's first page and includes unchanged/passed stories that get_build only counts.

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?

The description explicitly says when to use it: to read past get_build's first page or to browse unchanged/passed stories. It also gives follow-up guidance for retrieving images with get_diff or render_diff_image, helping the agent choose the correct tool chain.

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

All UI Verify toolsInspect
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
Disambiguation4/5

Most tools target distinct resources and actions, and the descriptions carefully separate build triage from PR changesets. However, get_diff and render_diff_image both provide diff imagery (URLs vs inline), and accept_build overlaps with review_diff's accept mode, so one or two selections could be mis-picked without reading closely.

Naming Consistency5/5

All nine tools use a consistent snake_case verb_noun pattern: list_* for paginated listings, get_* for detail/triage, render_* for image output, and review_diff/accept_build for review actions. The naming convention is predictable and easy to reason about.

Tool Count5/5

Nine tools is well within the ideal scope for a visual-regression review server. Each tool maps to a distinct workflow step—finding builds, triaging results, paging stories, fetching images, and recording reviews—without redundant or bloated additions.

Completeness5/5

The tool surface covers the full UI-verification loop: discover builds, inspect gate verdicts, page through changed/failed/unchanged stories, fetch diff details and inline images, review individually or bulk-accept, and inspect PR-level visual changesets. No essential operation for the stated domain is missing.

Resources