Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

explainVisualRun

Explains what changed in a visual run by identifying changed regions, describing text/CSS updates, and linking screenshot, baseline, and diff images.

Instructions

Explain what changed in a visual run: each changed region with what it is, an AI description of the change when the account has AI region names on, text and CSS changes from the page, plus links to the screenshot, baseline and diff images. Read-only.

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": {
      "runId": "<runId>"
    },
    "name": "explainVisualRun"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesID of the visual run.

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 comparatively well: it declares 'Read-only', discloses a conditional behavior ('an AI description of the change when the account has AI region names on'), and describes the returned payload shape. It stops short of covering auth requirements, failure modes for invalid or missing run IDs, or result size/pagination.

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?

One front-loaded sentence with a colon-delimited inventory of what is returned, ending with the safety flag 'Read-only'. The dense list is justified because each element describes distinct content in the response, though it could be broken up slightly for scanability.

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?

Because no output schema exists, the description must explain the return value, and it does so thoroughly for a read-only single-parameter tool. The remaining gap is routing guidance against the closely named reviewVisualRun and getVisualRuns siblings.

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?

There is a single required parameter, runId, and its schema coverage is 100% with a description ('ID of the visual run') plus numeric bounds. The prose adds nothing about the identifier's origin or format beyond the schema, so baseline 3 is appropriate.

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?

The description names a specific verb ('Explain what changed') and a specific resource ('a visual run'), then enumerates what the explanation contains: changed regions, AI change descriptions, text and CSS changes, and image links. An agent can tell this is an explanatory/inspection tool rather than a trigger tool, but the description never contrasts it with getVisualRuns or reviewVisualRun, so sibling differentiation is left implicit.

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 only implied: the agent can infer this is for understanding an already-completed run, and 'Read-only' signals it is safe to call. There is no explicit statement of when to prefer this over reviewVisualRun or getVisualRuns, and no stated prerequisites such as needing a completed run or the account-level AI region naming feature actually being on.

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