Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

tb_screenshot

Capture a PNG screenshot of the active browser session and save it to disk with a clickable file link. Use the optional savePath to choose the file or directory location.

Instructions

Capture a PNG screenshot of the active browser session. Returns a base64 image content block AND saves the PNG to disk, returning a clickable file:// link — many MCP clients (e.g. Claude Desktop) don't render tool-returned images inline, so the saved file is the reliable way for a human to view it. Pass savePath to control where it's written (a .png file path, or a directory); otherwise it goes to the OS temp dir.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "tb_screenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
savePathNoWhere to write the PNG: a full file path ending in .png, or a directory (a filename is generated). Relative paths resolve against the server's working directory. Defaults to the OS temp dir.
sessionIdYesSession ID from tb_openBrowser

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a good job: it discloses the dual return channel (base64 content block plus on-disk PNG), the file:// link, and the reason clients often need the saved file. It does not cover failure behavior, e.g. what happens with no active session or an unwritable path.

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 the action and then the return behavior, with no filler sentences. The long parenthetical rationale is justified since it explains a non-obvious dual-output design, though the paragraph could be tightened.

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 two-parameter read tool with no output schema and no annotations, the description covers the action, both return channels, and file placement defaults. Only error and session-state preconditions are left unstated.

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 savePath and sessionId are already fully documented in the schema. The description restates the .png-or-directory behavior and the temp-dir default 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.

Purpose4/5

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

States a specific verb and resource ("Capture a PNG screenshot of the active browser session"), which is concrete enough to act on. It does not differentiate itself from similarly-named siblings such as takeScreenshot, tb_snapshot, or getScreenshotList, so an agent must infer the distinction.

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?

Usage is implied by the phrase "active browser session" and the sessionId reference to tb_openBrowser, but there is no explicit statement of when to pick this over takeScreenshot or tb_snapshot. The rendering note explains why the saved file exists, not when to choose this tool.

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