Skip to main content
Glama
prakhar-gahlot

TestMu AI Test Manager MCP

by prakhar-gahlot
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Get Test Manager Test Run by ID

tm.get_testRunById

Retrieve a LambdaTest Test Manager test run by ID to view its title, status, type, build state, tags, and all test case instances with their assigned environments.

Instructions

Retrieves a LambdaTest Test Manager test run by its exact ID: title, objective, status, type (Manual/Automation), build state, tags, and every test case included in the run along with the environment(s) (browser/OS/device/resolution) each one is set to run against. Note: this does not include per-execution pass/fail results - the status shown per test case is its own review status, not an execution outcome; use tm.get_testExecutionHistoryByTestCaseId for actual run history. TERMINOLOGY: a 'test case instance' is ONE (test case x environment) pairing, not one test case. If a single test case is assigned 2 environments in this run, that is 2 instances, not 1 - the count of unique test cases in a run is virtually always smaller than the instance count. KNOWN API QUIRK (already corrected in this tool's output, for awareness only): the LambdaTest API's own total_test_cases/total_environments/total_run_instances fields on this endpoint are ALL THE SAME underlying number (the instance count) despite their distinct-sounding names. This tool does NOT trust those fields - the 'Test Cases (distinct)' and 'Environments (distinct)' figures shown below are computed directly from the instance list instead, so they ARE genuinely correct. tm.get_testRunsByProjectId independently reports correct distinct figures too (via different, non-quirky fields), so the two tools' numbers should agree for the same run - if they ever don't, that's worth flagging as a bug, not expected behavior. Read-only; does not modify anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
test_run_idYes

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: read-only nature, API quirk detailing how the tool corrects field inconsistencies, and clarifies that shown status is review status not execution outcome.

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?

The description is lengthy but efficient: every sentence adds unique value (inclusions, exclusions, terminology, quirk, cross-tool notes). Well-structured with front-loaded main purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and a simple input schema, the description thoroughly covers return value details, behavioral quirks, and cross-referencing with sibling tools, making the agent fully informed for correct invocation.

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?

The sole parameter 'test_run_id' is simple, but the description adds no extra semantics beyond the schema's type and minLength. While the parameter is self-explanatory, given 0% schema coverage, the description could have elaborated on format or examples.

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?

The description clearly states it retrieves a test run by ID, lists exactly what data is included (title, objective, status, type, build state, tags, test cases with environments) and explicitly notes what is excluded (execution results). It differentiates from siblings like tm.get_testRunsByProjectId and tm.get_testExecutionHistoryByTestCaseId.

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?

Provides explicit when-to-use (needing single run details) and when-not (for execution results, directing to alternative tool). Also provides terminology clarifications and cross-tool consistency checks, giving comprehensive usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/prakhar-gahlot/TestMu-AI-Test-Manager-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server