Skip to main content
Glama
Sentry MCP

Sentry MCP

Official
by getsentry

Get Snapshot Image

get_snapshot_image
Read-only

Retrieves a specific preprod snapshot image—current, previous, or diff screenshot—with metadata, returning a preview unless full resolution is requested.

Instructions

Get one image from a preprod snapshot: the current, previous, or diff screenshot, with its metadata. Returns a preview image unless full resolution is requested. Get image file names from get_snapshot or get_latest_base_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": {
      "snapshotId": "<snapshotId>",
      "imageIdentifier": "<imageIdentifier>"
    },
    "name": "get_snapshot_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoBypass cached reads.
regionUrlNo
snapshotIdYesNumeric snapshot artifact ID.
imageIdentifierYesImage file name exactly as get_snapshot lists it, including any slashes.
imageResolutionNo`full` returns the original bytes, which can make the response much larger.preview
organizationSlugNoThe organization slug, from `find_organizations`. In `org/project` notation, the part before the slash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely non-structured behavior: it returns a preview by default, full resolution is opt-in, and the response carries image metadata. It does not describe size limits or pagination, but the schema's imageResolution entry covers part of that.

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?

Three compact sentences with the core purpose front-loaded, followed by return behavior, then the prerequisite pointer. No filler or restated title text; every clause carries actionable information.

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?

There is no output schema, so the description must characterize the return value, and it does: an image plus metadata, preview by default. Combined with the annotations and high schema coverage, an agent has enough to call this correctly. The only gap is what happens on missing or stale snapshot IDs.

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 description coverage is 83%, so the schema already documents snapshotId, imageIdentifier, regionUrl, organizationSlug, and imageResolution. The description mainly reinforces where the image file name comes from, which the schema also states. Beyond noting that the identifier maps to current/previous/diff images, it adds little new parameter meaning.

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 verb and resource ('Get one image from a preprod snapshot') and immediately enumerates the three variants it covers: current, previous, or diff screenshot. That level of specificity lets an agent distinguish it from get_snapshot and get_latest_base_snapshot without opening either 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?

Explicitly routes the agent to the prerequisites: 'Get image file names from get_snapshot or get_latest_base_snapshot,' which tells the caller how to obtain the required imageIdentifier. The preview-versus-full-resolution default is stated as a usage rule. It stops short of naming when-not-to-use conditions, so it is not a full 5.

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