Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

reviewVisualRun

Approve or reject a visual run and optionally make the approved screenshot the new baseline for that browser.

Instructions

Approve or reject a visual run, the same as on its run page. Approving with makeBaseline=true also makes its screenshot the new baseline for that browser. Only do this when the user asked you to.

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>",
      "decision": "<decision>"
    },
    "name": "reviewVisualRun"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesID of the visual run.
decisionYesapprove (the change is intended) or reject.
makeBaselineNoWith approve: also make this screenshot the new baseline.

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, the description must carry the whole behavioral burden. It does disclose the important side effect that makeBaseline=true changes the baseline for that browser, which is real value beyond the name. However, it says nothing about permissions needed, whether a decision can be reversed, or what happens to the underlying run state after a reject.

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 with zero padding; the action and equivalence come first, the consequential side effect second, and the safety constraint last. Every sentence earns its place.

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?

For a 3-parameter mutation tool with full schema coverage and no annotations, the description covers purpose, guardrail, and the main side effect. It stops short of describing what the call returns (no output schema exists) and whether the decision is reversible, leaving an agent unable to predict the result of the call.

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 baseline is 3. The description reinforces the decision semantics and adds the 'for that browser' scoping of the baseline change, but does not add format or usage detail beyond what the schema already states for runId, decision, and makeBaseline.

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 pair (approve or reject) and the resource (a visual run), plus a useful equivalence: 'the same as on its run page.' It is clearly a write operation, distinguishable from the read siblings like getVisualRuns or explainVisualRun, though it never names an alternative explicitly.

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?

'Only do this when the user asked you to' is an explicit guardrail telling the agent not to act autonomously. It also clarifies the makeBaseline interaction with approve. What is missing is guidance on when rejection is appropriate versus leaving a run pending, or what to do if a run is already reviewed.

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