Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

takeScreenshot

Capture screenshots of a URL across multiple browsers and platforms, including localhost through an active TestingBot Tunnel. Returns a screenshot ID for retrieving results.

Instructions

Take screenshots of a URL across multiple browsers and platforms. Returns a screenshot ID to retrieve results. localhost / private-network URLs are captured through the account's newest running TestingBot Tunnel — start one with startTunnel first.

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": {
      "url": "<url>",
      "browsers": "<browsers>"
    },
    "name": "takeScreenshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to screenshot
browsersYesArray of browser configurations
fullPageNoCapture full page or just viewport
waitTimeNoTime to wait before taking screenshot (in seconds, max 60)
resolutionNoScreen resolution (e.g., '1920x1080')1920x1080

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full load; it does disclose the key asynchronous trait (an ID is returned rather than results) and the tunnel dependency. It does not state that each browser config likely produces a separate screenshot, nor anything about quota, auth level, or failure behavior for unsupported browser/OS combinations.

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 short sentences, purpose first, then the async return contract, then the precondition. Nothing is padded and the highest-risk constraint is placed where it will be read.

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?

No output schema exists, and while the description says a screenshot ID is returned, it never names the tool or step used to retrieve results, nor explains how multiple browser configurations map to multiple results. For an async multi-target tool this leaves a meaningful gap.

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 100%, so the schema already explains url, browsers, fullPage, waitTime, and resolution. The description only re-expresses the multi-browser aspect and adds no detail on the nested browser config or on how waitTime interacts with fullPage.

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?

Names a specific verb and resource ('Take screenshots of a URL across multiple browsers and platforms') and adds the important output fact that a screenshot ID is returned for later retrieval. It does not explicitly distinguish itself from retrieval siblings like getScreenshotList or tb_screenshot, so an agent must infer the split.

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 a concrete precondition and alternative: localhost/private-network URLs must go through the account's newest running TestingBot Tunnel, started with startTunnel. It lacks general guidance on when to prefer this over the other screenshot-related siblings, but the highest-risk usage case is covered.

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