Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getAccessibilityRuns

Retrieve accessibility test runs for a specific test ID, newest first, including scores and issue counts to review scan results.

Instructions

List the scans of one accessibility test, newest first, with score and issue counts.

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": {
      "testId": "<testId>"
    },
    "name": "getAccessibilityRuns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of runs (max 100).
offsetNoSkip this many runs.
testIdYesID of the accessibility test.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does add real behavior: result ordering and the shape of what comes back (scores, issue counts). It does not state read-only nature, pagination defaults/limits, or permissions, leaving meaningful gaps for an unannotated tool.

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 sentence with zero filler, front-loaded with the resource and scope; ordering and return contents follow naturally.

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 three-parameter read tool with full schema coverage and no output schema, the description covers scope, ordering, and returned fields. Only pagination behavior and a trivial hint of alternatives are missing.

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 coverage is 100% and the schema already documents testId, limit (max 100, default 10), and offset. The description only implicitly ties testId to 'one accessibility test' and adds nothing about pagination, so it sits at the baseline.

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 and resource ('List the scans of one accessibility test') plus ordering ('newest first') and the fields returned ('score and issue counts'). It is clearly distinct from getAccessibilityTests or getAccessibilityFindings, though it never names those siblings explicitly.

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?

The 'newest first' ordering and the score/issue-count mention imply the tool is for reviewing a test's scan history, but there is no explicit when-to-use, when-not, or routing to getAccessibilityFindings or getVisualRuns. Guidance is implied only.

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