Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getTests

Retrieve recent tests with optional pagination to review status, browser, platform, video, and duration details.

Instructions

Retrieve a list of recent tests with optional pagination. Returns test details including status, browser, platform, video and duration.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of tests to retrieve (default: 10, max: 100)
offsetNoOffset for pagination (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does usefully disclose the returned fields (status, browser, platform, video, duration), but says nothing about ordering semantics beyond "recent", whether results are scoped to the caller's project, rate limits, or what an empty list looks like.

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?

Two short sentences with the core action front-loaded and no filler. The second sentence about returned fields earns its place only because no output schema exists, though it is a slightly loose enumeration.

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 zero-required-parameter read/list tool, the definition covers purpose, pagination, and return contents, which is what an agent needs to invoke it. The remaining gaps (result ordering, scope of "recent", sibling routing) are minor given the shallow schema.

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 (default 10, max 100) and offset (default 0, min 0) are fully documented in the schema with defaults and bounds. The description only restates that pagination is optional, adding no format or interaction details beyond the schema, so the baseline 3 applies.

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?

"Retrieve a list of recent tests" states a specific verb and resource, plus a scope qualifier (recent). It is clear what the tool does, but it never names how it differs from near-identical siblings such as getTestDetails, getTestsForBuild, or getVisualTests, so the agent must infer the distinction from names alone.

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 implied rather than stated: the word "recent" and the optional pagination hint that this is a general browsing endpoint. There is no explicit when-to-use/when-not-to-use guidance and no pointer to getTestsForBuild for build-scoped results or getTestDetails for a single test, which are the natural alternatives.

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