Compose Preview Catalogs

ui_builder_list_revisions

A design's retained revisions, newest first: each one's number, who made it, when, the operation that produced it (setProperty ×2, insertNode, undo, restored r3) and its document digest. retention says how far back the history still reaches — older revisions are gone, and get, diff, restore and fork stop at that floor. Page with before. Read access.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Revisions per page. Defaults to 20.
`token`	No	A grant token from poll_access, when you cannot set the X-Compose-Preview-Token header yourself — an MCP client fixes its headers at connect time, so this is how a token approved during this session is used in it. Prefer the header where you control it.
`before`	No	Only revisions older than this one; pass the previous reply's `nextBefore`.
`designId`	Yes
`agentName`	No	Optional agent/client name shown to design viewers; self-reported.
`agentModel`	No	Optional current model name shown to design viewers; self-reported. Omit when unknown.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`schema`	Yes
`summary`	Yes
`designId`	Yes
`retention`	Yes
`revisions`	Yes
`nextBefore`	No
`currentRevision`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 4, 2026

addedInput schema / properties / agentModel

Added value: +{
+  "description": "Optional current model name shown to design viewers; self-reported. Omit when unknown.",
+  "maxLength": 80,
+  "type": "string"
+}

addedInput schema / properties / agentName

Added value: +{
+  "description": "Optional agent/client name shown to design viewers; self-reported.",
+  "maxLength": 80,
+  "type": "string"
+}

AddedOct 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses newest-first ordering, that retention defines a floor beyond which revisions are permanently gone, and that get/diff/restore/fork all stop at that floor. It also marks the operation as read access, which is the key safety signal an agent needs.

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?

Front-loads the resource and its ordering, then layers in retention and pagination detail in a compact form. The example operation strings add useful concreteness without serious bloat, though the sentence is dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be spelled out, yet the description still characterizes them helpfully. Combined with pagination and retention-floor context, an agent has enough to call this list tool correctly; only the sibling-routing guidance is thin.

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

Parameters3/5

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

Schema coverage is 83%, so the schema already documents most parameters including the `before` paging cursor and the token/agent fields. The description adds the 'page with before' hint but no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific resource and scope: a design's retained revisions, newest first, with the fields each entry carries. It implicitly distinguishes itself from restore/fork/diff by noting those operations stop at the retention floor, so an agent can tell it apart from the mutation siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives some usage context ('Read access', 'Page with before') and explains the retention floor that bounds this and related operations. However, it never explicitly states when to use this list versus siblings like ui_builder_restore_revision or ui_builder_diff_designs, leaving the routing to inference.

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

All Compose Preview Catalogs tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.