Skip to main content
Glama
Sign In

Meridian

by ai.the-meridian
OverviewDiscussions(2)Admin

List PR Previews

previews_list
Read-only

Lists the pull-request preview deployments for an app, newest first: each one's pr_number, head_sha, base_url, status, sanitised error_message and expires_at.

Use it after pushing a branch or opening a pull request to find the preview URL for that PR, and to check whether its build succeeded. A preview with a failed status and an error_message is the fastest signal that a change broke the build.

Optionally filter by pr_number. limit defaults to 20 and caps at 100. Previews expire, so an old PR may have no live preview.

Takes the app_id from apps_list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app_id": "<app_id>"
    },
    "name": "previews_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum previews to return. Default 20, maximum 100.
app_idYesThe app uuid returned by `apps_list`.
pr_numberNoOnly previews for this pull request number.
organization_idNoAn organisation uuid or slug. When supplied, `app_id` is resolved within that organisation and may be a slug instead of a uuid, mirroring the Meridian web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely new behavior: newest-first ordering, an expiry caveat meaning old PRs may have no live preview, and that error_message is sanitised. It does not discuss pagination mechanics or what an empty result means, so not a 5.

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-loaded with purpose and return fields, then usage, then filters, then a dependency note about app_id. Slightly verbose with some repetition of schema facts (limit default/max), but no sentence is wasted.

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?

With no output schema, the description compensates by listing the returned fields and their diagnostic meaning, plus the expiry caveat and the apps_list dependency for app_id. An agent has everything needed to call it correctly and interpret results.

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 100%, so all four parameters are already documented. The description restates pr_number filtering and the limit default/cap rather than adding new meaning, and it does not mention organization_id at all, so the baseline of 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?

The description opens with a specific verb+resource ('Lists the pull-request preview deployments for an app'), states ordering ('newest first'), and enumerates the returned fields, so an agent can tell it apart from siblings like deployments_list or app_get without opening the schema.

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?

It gives a concrete trigger ('after pushing a branch or opening a pull request to find the preview URL ... and to check whether its build succeeded') and a diagnostic use case for failed status plus error_message. It does not explicitly name an alternative tool or state when not to use it, which keeps it below a 5.

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

All Meridian toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources