Skip to main content
Glama

project_screenshots

Read-onlyIdempotent

Real picture of the deployed site for each recent version. The platform captures a desktop screenshot of the project's homepage after every deploy and stores it alongside the version history. Answers "what does this app look like right now" (e.g. for design / visual-editor workflows) and "did the last deploy change the way the homepage renders" (regression spot-check).

An optional version filters to a specific deploy.

By DEFAULT returns metadata only per screenshot (version, viewport, captured_at, size_bytes) — the large inline base64 image bytes are omitted to keep your context lean. include_data: true returns each as a data_url (data:image/png;base64,...) you can render with <img src={data_url}>; the browser tool sees and inspects the live page.

Example:

{ "project_id": "my-saas" }
// Returns (metadata only — data_url omitted by default):
{
  "project_id": "my-saas-uuid",
  "screenshots": [
    { "version": 12, "viewport": "desktop", "captured_at": "2026-05-19T...", "size_bytes": 142_321 },
    { "version": 11, "viewport": "desktop", "captured_at": "2026-05-18T...", "size_bytes": 138_004 }
  ]
}
// With include_data:true, each entry also contains: "data_url": "data:image/png;base64,..."

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": {
      "project_id": "<project_id>"
    },
    "name": "project_screenshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoOptional — filter to a single deploy version.
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).
include_dataNoOptional, default false. When false (default) the response omits the large inline base64 image bytes and returns metadata only — keeps your context lean. true returns the pixels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly and idempotent; the description adds substantial behavior: the default response omits base64 bytes and returns metadata only, `include_data:true` yields a `data:image/png;base64,...` data_url usable in `<img src>`, and the exact metadata fields returned. That is exactly the context-lean versus payload tradeoff an agent needs and cannot get from the annotations.

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 key fact (metadata by default, opt-in pixels) is front-loaded in bold, and the example earns its space by showing both default and include_data shapes. The prose is somewhat long for three parameters, but nothing is clearly redundant.

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?

There is no output schema, yet the description supplies the full return shape via a worked example plus the metadata field list, so an agent knows precisely what it will receive in both modes. Combined with annotation-covered safety profile, nothing needed to call it correctly is missing.

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% and the schema descriptions already explain `version` filtering, `project_id` resolution ('default' fallback, error listing projects), and the `include_data` default. The description mostly restates this with an example rather than adding new semantics, so the 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 (desktop screenshots captured per deploy of the project homepage) and a clear verb scope (retrieve). It distinguishes itself from the `browser` sibling by contrasting stored post-deploy captures with the live page the browser tool inspects, so an agent can choose 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?

Gives concrete use cases — 'what does this app look like right now' for design/visual-editor workflows and regression spot-checks after a deploy — and implicitly routes live inspection to the `browser` tool. There is no explicit when-not-to-use or named alternative for retrieving older version imagery (e.g. diff/rollback siblings), so it stops short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources