Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

tb_listSessions

Lists all active browser sessions managed by the server, helping you recover a lost sessionId. Mobile device sessions are not included.

Instructions

List all active browser sessions managed by this server. Useful when you've lost track of a sessionId. (Mobile device sessions are NOT listed here — they live inside appium-mcp; use appium_session_management with action 'list'.)

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.4/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 does add useful behavioral scope (server-scoped, excludes Appium mobile sessions), but says nothing about what each session entry contains, whether closed sessions are filtered out, or any auth/rate constraints.

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, the core action front-loaded, and the parenthetical exclusion placed after the main statement rather than interrupting it. Every clause earns 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 zero-parameter read tool this is nearly complete, but with no output schema the agent is left guessing the shape of the returned session records (ids, browser types, timestamps). The mention of 'sessionId' hints at it but does not define it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and the schema is fully closed, so there is no parameter meaning to add. Baseline applies; the description correctly implies an unfiltered full listing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb plus resource plus scope: 'List all active browser sessions managed by this server.' It immediately delimits the corpus as server-managed browser sessions, so an agent can tell it apart from screenshot, tunnel, and test-file listing siblings without opening any schema.

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

Usage Guidelines5/5

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

Gives a concrete triggering situation ('when you've lost track of a sessionId') and an explicit exclusion with an alternative ('Mobile device sessions are NOT listed here... use appium_session_management with action "list"'). Both the when and the when-not are stated.

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