Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Latest Base Snapshot

get_latest_base_snapshot
Read-only

Retrieve an app's baseline UI screenshots from preprod snapshots to inspect current screens, dark mode variants, or visual regression baselines; grouped by file name, display name, and description.

Instructions

Get an app's latest UI screenshots (baseline or golden images) from preprod snapshots, such as the current screens, dark mode variants, or the baseline behind a visual regression. Returns each image's file name, display name, and description, grouped. For a snapshot comparison by ID, use get_snapshot.

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": {
      "appId": "<appId>"
    },
    "name": "get_latest_base_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesApp identifier, such as `sentry-frontend` or `com.emergetools.hackernews`.
freshNoBypass cached reads.
branchNo
projectNo
regionUrlNo
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Output Schema

NameRequiredDescriptionDefault
appYes
urlYes
vcsYes
appIdYes
groupsYes
snapshotIdYes
totalImagesYes
responseNotesYes
organizationSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already establish this as a safe, read-only, open-world operation, lowering the disclosure burden. The description adds that images come from preprod snapshots and are grouped, but it does not mention caching behavior despite the fresh parameter or other operational constraints.

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 short and front-loads the core purpose and alternative. The clause listing returned fields is somewhat redundant because an output schema exists, but it is not a major structural issue.

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

Completeness3/5

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

With an output schema and annotations present, the description covers the main purpose and sibling routing well. However, for a six-parameter read tool with only 50% schema description coverage, it lacks enough guidance on branch, project, region, and caching parameters to be fully complete.

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

Parameters2/5

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

Schema description coverage is only 50% for six parameters, and the description does not explain how to use appId, branch, project, regionUrl, organizationSlug, or fresh. It adds little meaning beyond what the schema already provides and does not compensate for the coverage gap.

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 uses a specific verb and resource: getting an app's latest base UI snapshots from preprod. It explains the snapshot types covered and explicitly distinguishes this from the sibling tool get_snapshot, which is for comparison by ID.

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 clearly indicates the use case, retrieving latest baseline/golden images, and names an alternative for comparison by ID. It does not fully spell out when not to use the tool or prerequisites such as required org/project context.

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