Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getVisualTests

Lists hosted visual regression tests in your account, including ID, name, URL, browsers, and paused status, with limit/offset pagination.

Instructions

List the account's hosted visual regression tests (id, name, URL, browsers, paused).

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": "getVisualTests"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of tests (max 100).
offsetNoSkip this many tests.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.4/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 behavioral burden. It does disclose that results are account-scoped and read-only ('List') and names the fields returned, including the useful 'paused' status flag. It says nothing about pagination defaults, ordering, or what happens when the account has more tests than the limit, which are the remaining behavioral gaps.

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?

A single front-loaded sentence with the resource and scope stated first and the returned fields compressed into a parenthetical. Nothing is redundant and no sentence is wasted.

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 two-parameter, read-only listing tool with fully documented parameters, the definition is nearly sufficient; enumerating the returned fields compensates for the absent output schema. The only missing element is when to prefer this over getVisualRuns.

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% — both limit (max 100, default 20) and offset (skip count) are fully documented in the schema, so the baseline of 3 applies. The description adds nothing about paging semantics beyond what the schema already states.

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 uses a specific verb ('List') with a specific resource ('hosted visual regression tests') and scopes it to 'the account's', which tells an agent exactly what it retrieves. The parenthetical enumeration of returned fields (id, name, URL, browsers, paused) further sharpens the purpose. It does not, however, explicitly distinguish itself from sibling tools like getVisualRuns, leaving the tests-vs-runs distinction to be inferred from the names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus getVisualRuns or the other listing tools, and no stated prerequisites beyond the implicit 'account' scope. An agent must infer that this is the discovery step and getVisualRuns is the execution-history step.

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