Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getTestDetails

Retrieves detailed test information by session ID, including logs, screenshots, video URLs, and execution metadata.

Instructions

Get detailed information about a specific test by session ID. Includes logs, screenshots, video URLs, and execution metadata.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "getTestDetails"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYesThe session ID of the 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 full burden. It usefully discloses the shape of the response (logs, screenshots, video URLs, execution metadata), which is genuine behavioral context beyond the schema. However it does not state that this is a safe read-only operation, nor what happens with an unknown or expired session ID, nor anything about response size or pagination for what is clearly a heavy payload.

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, front-loaded with the action and scope, followed by a compact enumeration of the return contents. No filler, no restatement of the tool name, nothing that fails to earn its place.

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 single-parameter read tool with no output schema, the description supplies both the identification key and an inventory of what comes back, which is what an agent needs to decide to call it and to anticipate the result. The remaining gap is the absence of any safety or failure-mode statement, which is minor for a 'get' operation.

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?

Only one parameter exists and its schema description is fully covered ('The session ID of the test'), so the schema does the work. The description adds only the qualifier 'by session ID', with no guidance on where a session ID comes from or what format it takes. Baseline 3 is appropriate.

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 ('Get detailed information about a specific test') and scopes it to a single test identified by session ID, which clearly separates it from list-style siblings like getTests or getTestsForBuild. It goes further by naming the payload (logs, screenshots, video URLs, execution metadata). It stops short of naming a specific sibling alternative, so it lands at 4 rather than 5.

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 'by session ID' framing implies this is the lookup tool to use when you already hold a session ID, versus listing tools for discovery, but that contrast is never made explicit. There is no statement about prerequisites, when not to use it, or which sibling to reach for instead (e.g. getMaestroFlowDetails). Usage is inferable but not stated.

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