Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getVisualRuns

List visual test runs newest first, filter by result or test ID, and paginate results to review screenshot comparisons and unreviewed failures.

Instructions

List visual runs (one browser's screenshot compared with its baseline), newest first. Use state=unreviewed to find failed runs nobody has rejected yet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getVisualRuns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of runs (max 100).
stateNoFilter by result.
offsetNoSkip this many runs.
testIdNoOnly runs of this visual test.

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 present, the description carries the full burden. It does disclose the default ordering ('newest first'), and 'List' implies a non-mutating read, but it says nothing about pagination behavior, result volume, or what a run record contains.

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 short sentences, the resource definition is front-loaded, and the actionable filter tip follows. Every clause adds information; nothing is padding.

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 simple read-only list tool with four fully documented optional parameters and no output schema, the description covers purpose, ordering, and the most valuable filter. It could say slightly more about pagination or the relationship to explainVisualRun/reviewVisualRun, which are the natural follow-ups.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning beyond the enum: it clarifies that 'unreviewed' means failed runs that have not yet been rejected, which the bare enum value 'unreviewed' does not convey. The other parameters (limit, offset, testId) are left entirely to the schema.

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 first sentence gives a specific verb and resource (list visual runs) and even defines what a run is: one browser's screenshot compared with its baseline. It does not, however, distinguish this from siblings such as getVisualTests (tests vs. runs) or explainVisualRun, so an agent must infer that boundary.

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?

It offers one concrete usage recipe — state=unreviewed to surface failed runs nobody has rejected yet — which is genuinely helpful routing advice. But there is no guidance on when to prefer explainVisualRun or reviewVisualRun, nor any exclusion of when not to use this tool.

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