Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getFailureLogs

Fetch session logs for a test by session ID to debug failures; use failuresOnly to return only error, exception, and stack-trace lines.

Instructions

Fetch and return session log file content (selenium, browser, chrome, vm, appium) for a test by session ID. Use this to debug failures — pass failuresOnly=true to extract only error/exception/stack-trace lines.

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

Input Schema

NameRequiredDescriptionDefault
logTypesNoWhich log types to fetch. Defaults to every type available on the test. Valid: selenium, browser, chrome, vm, appium.
sessionIdYesThe session ID of the test
timeoutMsNoPer-log fetch timeout in milliseconds (default 15000).
failuresOnlyNoIf true, only return lines that match error/exception/stack-trace patterns (plus 1 line of context above/below).
maxBytesPerLogNoTruncate each log to the last N bytes (default 50000, max 1000000). Failure context typically lives near the end.

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?

No annotations are supplied, so the description carries the full burden; it does establish this is a read-only fetch (lower risk) and discloses the failure-filtering behavior. It says nothing about what happens when a log type is unavailable for a session, whether results are large/costly to retrieve, or what shape the response takes, leaving notable 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?

Two sentences, front-loaded with the verb and resource, then immediately the use case and the key optional flag. Nothing redundant or padded.

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?

No output schema exists, so the description should convey the return shape, yet it only says 'log file content' without indicating whether results are returned per log type, concatenated, or truncated (truncation is only in the schema). For a debugging fetch tool with five parameters and no annotations, this leaves the agent guessing about response structure.

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 all five parameters are already documented with defaults, ranges and enums. The description restates failuresOnly semantics that the schema already spells out and merely parenthesizes the log type values, adding little meaning beyond structured fields.

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?

Names a concrete verb and resource: 'Fetch and return session log file content ... for a test by session ID', and enumerates the log sources (selenium, browser, chrome, vm, appium), so the agent knows exactly what comes back. It does not differentiate itself from sibling debug-oriented tools such as getAiFailureAnalysis or analyzeTestFailure, so the sibling-distinction bar for a 5 is not met.

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?

'Use this to debug failures' gives a clear situational trigger, and 'pass failuresOnly=true to extract only error/exception/stack-trace lines' prescribes a concrete usage pattern. There is no explicit when-not guidance or named alternative for the AI-analysis path, which keeps it out of 5 territory.

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