Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

retrieveScreenshots

Fetch screenshot results by screenshot ID and get URLs to generated screenshots for review or sharing.

Instructions

Retrieve screenshot results by screenshot ID. Returns URLs to the generated screenshots.

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": {
      "screenshotId": "<screenshotId>"
    },
    "name": "retrieveScreenshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
screenshotIdYesThe screenshot ID from takeScreenshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the return payload (URLs to generated screenshots), which is useful behavioral context, but it says nothing about whether results can be pending/unavailable, whether the URL expires, or how failures are surfaced — meaningful gaps for a retrieval tool with zero annotation coverage.

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?

Two brief sentences with zero filler; the primary action and the return value are both front-loaded and immediately readable.

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?

For a one-parameter lookup with no output schema, the description covers the essential contract by stating what is returned (URLs). It is only slightly incomplete in not addressing pending or failed screenshot states and URL lifetime.

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 there is a single required parameter, so the schema already documents screenshotId fully. The description adds only the concept that the ID comes from a screenshot-taking step, which the schema field description also conveys; no new syntax or format detail is added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Retrieve screenshot results by screenshot ID") and adds what comes back (URLs to generated screenshots), which separates it from a list-style sibling such as getScreenshotList. It stops short of naming an alternative explicitly, so the differentiation is implied by the singular "screenshot ID" rather than stated.

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?

The schema's parameter note ties the call to a prior takeScreenshot invocation, giving an implied workflow context, and the description implies single-result lookup. However, there is no explicit when-to-use versus when-not guidance (e.g., do not call before the capture completes, use the list tool for many results).

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